On Thu, Oct 18, 2007 at 11:24:41PM -0400, Nicolas Pitre wrote: > Frankly, I think effort should be spent on the refs update display at > this point. Something that looks like: Also agreed. > * refs/heads/origin: fast forward to branch 'master' of git://gi > t.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 > old..new: 66ffb04..4fa4d23 > > [...] > > You usually get long lines that gets wrapped, so that means 3 lines of > screen space for one updated branches. Is the "66ffb04..4fa4d23" > information really useful? Might someone ever care? I have used it occasionally when tracking repos to see what new commits have happened. Usually I use a separate branch to mark "what I've seen" (i.e., fetch, gitk origin..master, pull), but if it's a branch that I'm not actively tracking, the display is useful. What is really useless in that line is the fact that _every_ ref is going to have the name of the remote, even though we only support fetching from one remote at a time. Perhaps something like: Fetching from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 * refs/heads/origin: fast forward to branch 'master' although that URL is almost a line by itself. :) Also, why do we abbreviate "refs/heads/master" from the remote, but we don't abbreviate refs/heads/origin for the local? Maybe something like: * local heads/origin -> remote heads/master (fast forward) or for separate remote * local remotes/origin/master -> remote heads/master (fast forward) Thoughts? -Peff - 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
