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

Re: reflog weirdness

From
TNThien-Thi Nguyen <ttn@gnuvola.org>
Date
Dec 28, 2007, 21:35 UTC
Message-ID
<87prwqec4a.fsf@ambire.localdomain>
In-Reply-To
<7vhci2ectr.fsf@gitster.siamese.dyndns.org>

() Junio C Hamano <gitster@pobox.com> () Fri, 28 Dec 2007 13:20:16 -0800

   $ vi .git/logs/HEAD
   and truncate that line after "commit: " to remove the
   part that would normally show the one-line commit log
   message.

thanks for the tip. i'll do that as soon as i've had a chance to ponder the repercussions. in the meantime...

   How does commit 20d9d23 look like (the tracked contents
   are not interesting --- the commit log message is)?

here is the (again, not inlined due to strange bytes) top of "git show 20d9d23" output:

i see that the body of the log message (three bytes) corresponds to the first three bytes of the associated line in .git/logs/HEAD.

thi
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “reflog weirdness”
  1. Thien-Thi NguyenDec 28, 2007
  2. Junio C HamanoDec 28, 2007
  3. Thien-Thi NguyenDec 28, 2007
  4. Junio C HamanoDec 28, 2007
  5. Thien-Thi NguyenDec 28, 2007
  6. Junio C HamanoDec 29, 2007
  7. Thien-Thi NguyenJan 2, 2008

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.