"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes:
> Users may also now use `git-pull . foo~3` to merge the early part
> of branch foo. This was not previously possible as git-fetch does
> not know how to fetch foo~3 from a repository.
I personally think this is not an improvement, but rather a new
source of confusion. If the user wants a local merge, there is
'git-merge'. And the distinction between the commands makes it
clear that local merge can merge any commits exactly because
they are available locally, while remote fetch+merge needs to
choose from what the remote side offers so not arbitrary commits
like foo@{3.days.ago} cannot be pulled.
Also I thought there was a configuration variable that talks
about "remote = ." (didn't I merge that patch -- I do not
remember offhand) and I wonder how that interacts with this
change.
How much performance gain are we talking about here?
-
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