Junio C Hamano wrote
> If you use --local, that is equivalent to "cp -R". Your corruption
> in the source will faithfully be byte-for-byte copied to the
> destination. If you do not
> transport layer will notice
> object corruption.
> The difference between --mirror and no --mirror is a red herring.
> You may want to ask Jeff Mitchell to remove the mention of it; it
> only adds to the confusion without helping users.
Just to clarify, I don't know Jeff Mitchell personally, and I'm not
affiliated with the KDE project. I happened to have recently implemented a
backup strategy for a different codebase, that relies on `git clone
--mirror` to take the actual snapshots of the live repos, and I read about
Jeff's experiences, and that's why I started following this discussion.
Apologies if my questions are considered slightly off topic -- I'm not
positive if this is supposed to be a list for developers, and not users.
Nevertheless, I will try to contact Jeff and point him at this. My initial
reading of his blog posts definitely gave me the impression that this was a
--mirror vs. not issue, but it really sounds like his main problem was using
However, I think there may be room for some additional clarity in the docs.
The --local option in git-config(1) says "When the repository to clone from
is on a local machine, this flag bypasses the normal "git aware" transport
mechanism". But there's no mention of the consequences of this transport
bypass. There's also no mention of this in the "GIT URLS" section that
discusses transport protocols, and I also don't see anything noting it in
either of these sections of the git book:
View this message in context:
Sent from the git mailing list archive at Nabble.com.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html