On 2006-11-03 04:25:40 -0500, Sean wrote:
> Yeah.. Although fetching multiple remotes makes more sense as an
> optimization, especially when using a separate remotes namespace.
That's what "git fetch" is for. :-)
> Perhaps the real confusion is created because the only porcelain
> level merge command current in Git is "git pull .". A separate name
> might make things easier to grasp.
Indeed. Having pull = fetch + merge and not having a porcelain merge
command is not good, usability-wise. As is, one _has_ to learn the
weird ways of pull even if one is only interested in using separate
commands to fetch and merge.
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
-
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