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

Re: [PATCH 3/3] show-branch --reflog: show the reflog message at the top.

From
Junio C Hamano <junkio@cox.net>
Date
Jan 20, 2007, 00:23 UTC
Message-ID
<7v4pqmczqa.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0701200116280.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> does this mean you did not get used to "--walk-reflogs"? Just wanna know.
That's independent.

I still am having a hard time trying to explain what these commands would do, and why they might be useful:

	git-log --walk-reflogs master..next
	git-log --walk-reflogs master -- Documentation/
On the other hand I can understand why this might be useful:
	git-log --walk-reflogs master
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 11 in “show-branch --reflog: show the reflog message at the top.”
  1. 3/3 show-branch --reflog: show the reflog message at the top.Junio C Hamano, Jan 19, 2007
  2. Johannes SchindelinJan 20, 2007
  3. Junio C HamanoJan 20, 2007
  4. Johannes SchindelinJan 20, 2007
  5. Junio C HamanoJan 20, 2007
  6. Johannes SchindelinJan 20, 2007
  7. Junio C HamanoJan 20, 2007
  8. --walk-reflogs: disallow uninteresting commitsJohannes Schindelin, Jan 20, 2007
  9. Junio C HamanoJan 20, 2007
  10. Johannes SchindelinJan 20, 2007
  11. Junio C HamanoJan 20, 2007

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.