I've never used Bk and I really appreciate your comments here.
I agree, but I wonder why you are pulling/fetching (with or
without merge) if you are operating on your local development
branch (implying that you are in the middle of something else).
I would rather say "use 'git branch' to make sure if you are
ready to merge". Who teaches not to use "git pull"?
I have to disagree with this. In the simplest CVS-like central
repository with single branch setup in which many "novice users"
start out with, there is almost no need for "git fetch" nor
tracking branch. You pull, resolve conflicts, attempt to push
back, perhaps gets "oh, no fast forward somebody pushed first",
pull again, then push back. So I am not sure where "you really
do not want to use pull. trust me" comes from.
It is a different story for people who _know_ git enough to know
what is going on. They may be using multiple branches and
interacting with multiple remote branches, and there are times
you would want fetch and there are other times you would want
pull. But for them, I do think the suggestion would never end
with "trust me" -- they would understand what the differences
are.
-
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