From: Kristoffer Haugsbakk Date: Sat, 16 Nov 2024 14:54:54 +0000 (+0100) Subject: Documentation/git-bundle.txt: discuss naïve backups X-Git-Tag: v2.48.0-rc0~47^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=820fd1a5694b8d96609590163088d3f14731b565;p=thirdparty%2Fgit.git Documentation/git-bundle.txt: discuss naïve backups It might be naïve to think that those who need this education would end up here in the first place. But I think it’s good to mention this high-level concept here on a command which provides a backup strategy. Signed-off-by: Kristoffer Haugsbakk Signed-off-by: Junio C Hamano --- diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt index eaa16fc4b8..504b8a8143 100644 --- a/Documentation/git-bundle.txt +++ b/Documentation/git-bundle.txt @@ -344,6 +344,24 @@ You can also see what references it offers: $ git ls-remote mybundle ---------------- +DISCUSSION +---------- + +A naive way to make a full backup of a repository is to use something to +the effect of `cp -r `. This is discouraged since +the repository could be written to during the copy operation. In turn +some files at `` could be corrupted. + +This is why it is recommended to use Git tooling for making repository +backups, either with this command or with e.g. linkgit:git-clone[1]. +But keep in mind that these tools will not help you backup state other +than refs and commits. In other words they will not help you backup +contents of the index, working tree, the stash, per-repository +configuration, hooks, etc. + +See also linkgit:gitfaq[7], section "TRANSFERS" for a discussion of the +problems associated with file syncing across systems. + FILE FORMAT -----------