public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: unpacking git files
Date: Thu, 23 Apr 2020 17:07:50 -0500	[thread overview]
Message-ID: <20200423170750.2f6355d3@bigbox.attlocal.net> (raw)
In-Reply-To: <alpine.NEB.2.21.2004231711080.12964@panix1.panix.com>

Tim here.

I'm not sure what sort of "git file" you have.  If it's a "bundle",
you can pull from it as if it was an upstream project:

  git clone your_repo.bundle repo

to create a local directory called "repo" and clone that bundle into
it.

If it's just a pack file from inside the .git/ folder from another
repo, there's no telling what may or may not be in there (okay, one
can spelunk in there, but you lose a lot of the metadata that is
elswhere in the folder such as branch-heads/names, and any commits
that weren't part of the pack-file)

-tim

On April 23, 2020, Linux for blind general discussion wrote:
> If you download a git file how is it possible to have git unpack
> the file for you into its own directory tree?
> I failed to write my git credentials in braille and haven't used
> them for a very long time so may be able to get a git file using
> wget but for now I don't know how to unpack the file.
> 
> 
> 
> --
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
> 

  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
 ` Linux for blind general discussion [this message]
   ` Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200423170750.2f6355d3@bigbox.attlocal.net \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).