On Thu, Oct 18, 2007 at 11:50:39PM -0400, Nicolas Pitre wrote:
> Maybe we should have a shortcut notation for <ref>@{1}..<ref> instead?
> I end up using that all the time since the fetch result has long
> scrolled off the screen when I want to look at what was fetched.
I must confess to never using reflogs in that case...for some reason
they just never come to mind. But now that you and Shawn mention them,
there's really no reason to leave the hash..hash for the fetch.
As for a shortcut notation, what about allowing '..' notation inside a
reflog. I.e., <ref>@{a..b} is the same as <ref>@{a}..<ref>@{b}? So you
could perhaps do origin/master@{1..}?
I'm not sure if there are syntactic issues with parsing out the '..' (or
'...') operator.
> > although that URL is almost a line by itself. :)
> It is, therefore I'd skip "Fetching from " entirely.
Yes, I was tempted to suggest that. I think it might need some context,
depending on what comes right before it.
> That looks fine for a push. I'd say "remote foo -> local bar" for a
> fetch.
Agreed.
-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
