This is actually a perfect example for
- a script that is porcelain as well as plumbing (you are supposed to use
it directly, or via pull), and for
- a terrible UI.
_If_ you use git-fetch directly you virtually always want to store the
result. I was tempted quite often to submit a patch which adds a command
line switch --no-warn, which is passed to git-fetch by git-pull, and
without which git-fetch complains if the branch-to-be-fetched is not
stored right away (and refuses to go along).
_Also_, git-pull not storing the fetched branches at least temporarily
often annoyed me: the pull did not work, and the SHA1 was so far away I
could not even scroll to it. The result: I had to pull (and fetch!) the
whole darned objects again. Again, I was tempted quite often to submit a
patch which makes git-pull fetch the branches into refs/fetch-temp/* and
only throw them away when the merge succeeded.
Ciao,
Dscho
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
