Re: What's cooking in git.git (topics)
- From
Brian Gernhardt <benji@silverinsanity.com>
- Date
- Dec 17, 2006, 04:35 UTC
- Message-ID
- <3C540990-B78E-405B-ACFF-F558DB776C85@silverinsanity.com>
- In-Reply-To
- <7vodq3a136.fsf@assigned-by-dhcp.cox.net>
Show 7 quoted lines
> ** jc/reflog (Thu Dec 14 15:58:56 2006 -0800) 1 commit > - Teach show-branch how to show ref-log data. > > A strawman to make reflog data a bit more browsable; it would be > useful while recovering from a mistake you made recently. Not > essential and can wait or be dropped if people do not find it > useful.
I'd prefer not to add clutter into show-branch. I use it on a regular basis to see what I've added to what topic branch recently, and to look at branches before rebasing. It also just seems like the wrong place to have that kind of data, although I guess it's more useful for people who do merges more often than I do.
What about a "git reflog [<branch>]" command instead? Would show output similar to "git log" (or "git show-branch" for brevity).