Shawn Pearce <spearce@xxxxxxxxxxx> writes:
> The --mirror-all option to git-fetch can be used to obtain a copy of
> every available remote ref into the current repository. This can be
> a rather destructive update as the local repository will have its
> HEAD ref overwritten, as well as any ref which it shares in common
> with the remote repository.
I can sort of see where something like this is very much useful,
but it sounds like a tool quite different from git-fetch.
(1) I really do not like rolling this kind of speciale purpose
command into git-fetch, which is frequently used by end
users, to avoid mistakes.
If there is reluctance against adding yet another new
command (and there certainly is), this feels more like a
cousin of "git-clone --bare".
(2) Although there is no inherent reason not allowing a working
tree associated with the repository that is kept updated
this way, the user will be utterly confused in a working
tree whose current branch head is updated like this, until
the working tree and the index is matched to the updated
HEAD. It might be reasonable to run checkout -f HEAD when
a working tree is associated with the repository (the
command is screwing over even the current branch HEAD, so
losing what happened to be in the working tree is really
not an issue), but as a much easier safety measure we might
want to allow this mode of updating only on a bare
repository (that is, .git/index should not exist).
(3) This feels primarily meant for something like Pasky is
trying to run --- mirrored distribution point of git
repositories perhaps displayed with gitweb. When updating
such a repository, you would want to do things like running
update-server-info and automatically repacking the object
store. Especially the latter would be an interesting topic
(the archive vs active repacking strategy we talked about,
combined with set of packs with staggered spans to help
commit walkers Pasky talked about quite a while ago).
> ...
> such as if you are providing Git repository hosting and mirroring
> source repositories on other systems.
>
> Currently local refs are not deleted even if they do not exist in the
> remote repository. This may be taken as either a feature or a bug.
For that purpose I would say that is definitely a bug.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html