From: kristofferhaugsbakk@fastmail.com Date: Sun, 20 Oct 2024 19:15:02 GMT Subject: [PATCH 4/4] Documentation/git-bundle.txt: discuss naïve backups Message-ID: <63a431537b78e2d84a172b5c837adba6184a1f1b.1729451376.git.code@khaugsbakk.name> In-Reply-To: From: Kristoffer Haugsbakk 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 --- Notes (series): Correct mention of the section? All-caps seems to be the convention. Documentation/git-bundle.txt | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt index cf25e6e8540..b5cc4746b45 100644 --- a/Documentation/git-bundle.txt +++ b/Documentation/git-bundle.txt @@ -324,6 +324,20 @@ 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 -a `. 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]. + +See also linkgit:gitfaq[1], section "TRANSFERS" for a discussion of the +problems associated with file syncing across systems. + FILE FORMAT ----------- -- 2.46.1.641.g54e7913fcb6