git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why not show ORIG_HEAD in git-log --decorate?

From
Jeff King <peff@peff.net>
Date
Apr 10, 2010, 09:04 UTC
Message-ID
<20100410090441.GA18772@coredump.intra.peff.net>
In-Reply-To
<20100410090042.GA13109@atjola.homenet>
On Sat, Apr 10, 2010 at 11:00:42AM +0200, Björn Steinbrink wrote:
Show 12 quoted lines
> > I think most people do something like:
> > 
> >   gitk HEAD^..ORIG_HEAD
> > 
> > To see everything in ORIG_HEAD that isn't in HEAD^ (the first parent of
> > HEAD, or what you had just before the pull).
> 
> I guess you meant to say "gitk ORIG_HEAD.." there. ORIG_HEAD is already
> the pre-pull state. So if the merge actually created a merge commit,
> then HEAD^ == ORIG_HEAD, and if it was a fast-forward, then ORIG_HEAD is
> either the same as HEAD^ or one of its ancestors. In either case,
> HEAD^..ORIG_HEAD will be empty.
Urgh, yes. Sorry, I was totally not thinking when I wrote that.

I never use ORIG_HEAD, as I always do a fetch + inspect + merge, rather than pull. But I can't even figure out what thought process led me to write what I did above.

Thanks for the correction.
-Peff
Previous: Björn Steinbrink
Message 4 of 4 in “Why not show ORIG_HEAD in git-log --decorate?”
  1. Yury PolyanskiyApr 9, 2010
  2. Jeff KingApr 10, 2010
  3. Björn SteinbrinkApr 10, 2010
  4. Jeff KingApr 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.