Thanks Rich (& Michael)... Will use git bundle then.
Apreciated! On 9/4/2015 6:32 PM, Rich Freeman <[email protected]> wrote: > On Fri, Sep 4, 2015 at 1:19 PM, Michael Orlitzky <[email protected]> wrote: >> On 09/04/2015 01:09 PM, Tanstaafl wrote: >>> Similar to the recent thread on cloning... >>> >>> I don't know and have never even used Git, but I need to get a complete >>> and total backup of an entire Git repository to a single file that can >>> then be cloned into a new git repo on another system. This was for a >>> software project that was being developed by some off-site developers. >>> >>> What is the proper way to do this? Is it the 'git bundle' command? >>> >> >> The entire git repo is a single .git directory at the top level of your >> project. So you can bundle the whole thing with >> >> tar -cf project.tar /path/to/your/project > > I realize you're using the term "bundle" in the generic sense, but > there is a git term called a bundle and it isn't just a tarball of a > repository. > > I'd definitely recommend using "git bundle" for this. That is > basically what it was designed for, and I'd expect it to be more space > efficient since you won't have all the checked-out files. Presumably > git will make sure the bundle is packed and garbage-collected as well. > You can also perform operations like fetch/clone/etc from a bundle > without having to extract it first, which might be useful if you > wanted to merge it into another repository. This is pretty-much how > we've been moving around git repositories as part of the migration > project. >
