I'm burning my stuff on a dvd, before a quick reinstall. Never done that with git, being a recent user. So I'm just checking with you guys. If I understood correctly, I just need to backup my project directory project_name (which has .git inside it) watching for hidden files along with it, and when I copy it onto the "new" machine, and install git again, I resume like nothing happened ? Correct ?
the shortest, and the most worry relieving answer ever :)
ldigas
2010-01-12 05:43:27
I tried just saying "yep." but it won't let me post answers smaller than 15 characters :P A git repository is simply a folder(and it's sub folders) with a .git directory initialized with git init. you can move this folder anywhere and it will work with git.
Charles Ma
2010-01-12 05:47:19
I'm new to Git too, hence coming upon this question. Even though `git bundle` seems like a better option according to other answers here, if backing up files manually, surely only the _.git_ folder needs to be backed up? Can the current state of any branch be reconstituted properly from just that folder's contents?
Drew Noakes
2010-05-25 16:37:58
+7
A:
I would prefer git archive (that way, I do not have to "watch for hidden file")
The script git-archive-all.sh will actually archive all git repositories and submodules in the current path.
Useful for creating a single tarfile of a git super-project that contains other submodules.
As Charles Bailey rightly mentions in the comments, git bundle is more appropriate, to preserve the history. (git bundle was introduced in February 2007).
See Backing up a git repository with git bundle
git bundlewas designed to allow transfer of git commits when there is no direct connection between repositories (i.e.: offline) but using patches is not an option because of the large number of commits and multiple branches.
Agit bundleis just one file which can be very easily created and again imported as it can be treated like another remote. A quick example:
jojo@dualtron:~/devel$ git bundle create ~/devel.bdl master test
and a bundle is saved under
~/devel.bdlcontaining my master and test branches.
If I am now at repository B I just usejojo@dualtron:~$ git ls-remote devel.bdlwhich shows me the branches stored in the bundle.
To use the bundle I simple treat it like a remote, using git fetch (for example)
jojo@dualtron:~/git/repoB$ git fetch ~/devel.bdl refs/heads/\*:refs/remotes/bundle/\*
VonC
2010-01-12 06:28:21
For a backup, I think that `git bundle` is more appropriate than `git archive`. `git archive` just creates tarballs of trees (snapshots) but doesn't preserve commits and history. `git bundle` create without any dependencies can be a freeze dried repository of as many branches as you like.
Charles Bailey
2010-01-12 07:45:33
Is there any advantage in using "git bundle ..." over just select all/copy/paste the whole lot ? For this specific case (just burning to dvd or placing on usb temporarily) ?
ldigas
2010-01-12 16:19:30