# reflog weirdness 7 messages from 2007-12-28 to 2008-01-02. Participants: Thien-Thi Nguyen, Junio C Hamano. Thread: https://gitlist.dev/t/11414 ## Thien-Thi Nguyen, 2007-12-28 19:57 Subject: reflog weirdness Message-ID: <87ve6iegny.fsf@ambire.localdomain> URL: https://gitlist.dev/e/87ve6iegny.fsf%40ambire.localdomain ``` hello, i use git-1.5.3.5 and see the following fragment from "git reflog" (not inline due to binary values): i'd like to get rid of (or somehow get git to hide) the {21} line. any hints? thi ``` ## Junio C Hamano, 2007-12-28 21:20 Subject: Re: reflog weirdness Message-ID: <7vhci2ectr.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vhci2ectr.fsf%40gitster.siamese.dyndns.org In-Reply-To: <87ve6iegny.fsf@ambire.localdomain> ``` Thien-Thi Nguyen writes: > i'd like to get rid of (or somehow get git to hide) the {21} line. > any hints? $ vi .git/logs/HEAD and truncate that line after "commit: " to remove the part that would normally show the one-line commit log message. It would be more interesting to know why garbage follows "commit: " on that one entry, though. How does commit 20d9d23 look like (the tracked contents are not interesting --- the commit log message is)? ``` ## Thien-Thi Nguyen, 2007-12-28 21:35 Subject: Re: reflog weirdness Message-ID: <87prwqec4a.fsf@ambire.localdomain> URL: https://gitlist.dev/e/87prwqec4a.fsf%40ambire.localdomain In-Reply-To: <7vhci2ectr.fsf@gitster.siamese.dyndns.org> ``` () Junio C Hamano () 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 ``` ## Junio C Hamano, 2007-12-28 22:01 Subject: Re: reflog weirdness Message-ID: <7vtzm2cwbw.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vtzm2cwbw.fsf%40gitster.siamese.dyndns.org In-Reply-To: <87prwqec4a.fsf@ambire.localdomain> ``` Thien-Thi Nguyen writes: > 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. Thanks. Was it a buggy "git commit" command, or a bad commit log message was fed to "git commit" by the user, and there is nothing for me to worry about? ``` ## Thien-Thi Nguyen, 2007-12-28 22:44 Subject: Re: reflog weirdness Message-ID: <87fxxme8x9.fsf@ambire.localdomain> URL: https://gitlist.dev/e/87fxxme8x9.fsf%40ambire.localdomain In-Reply-To: <7vtzm2cwbw.fsf@gitster.siamese.dyndns.org> ``` () Junio C Hamano () Fri, 28 Dec 2007 14:01:55 -0800 Was it a buggy "git commit" command, or a bad commit log message was fed to "git commit" by the user, and there is nothing for me to worry about? i'm sorry, even though it was only a couple days ago, the actual events are far back in my memory, so i can't say. i wouldn't worry about it -- probably user error. (i'm new w/ git. most of the time i drive it from w/in emacs, which is well behaved; it is when i leave that comparative safety to do some flailing from the command-line that things go weird.) i suppose one way to improve git would be to test how it handles interruption (control-c in the middle of a commit, for example). a bit tricky to arrange (reproducibly), though... now i go search the docs for how to replace that log message. thi ``` ## Junio C Hamano, 2007-12-29 00:06 Subject: Re: reflog weirdness Message-ID: <7vprwqcqk3.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vprwqcqk3.fsf%40gitster.siamese.dyndns.org In-Reply-To: <87fxxme8x9.fsf@ambire.localdomain> ``` Thien-Thi Nguyen writes: > () Junio C Hamano > () Fri, 28 Dec 2007 14:01:55 -0800 > > Was it a buggy "git commit" command, or a bad commit log > message was fed to "git commit" by the user, and there is > nothing for me to worry about? > > i'm sorry, even though it was only a couple days ago, the actual > events are far back in my memory, so i can't say. i wouldn't > worry about it -- probably user error. (i'm new w/ git. most of > the time i drive it from w/in emacs, which is well behaved; it is > when i leave that comparative safety to do some flailing from the > command-line that things go weird.) > > i suppose one way to improve git would be to test how it handles > interruption (control-c in the middle of a commit, for example). > a bit tricky to arrange (reproducibly), though... > > now i go search the docs for how to replace that log message. "git-rebase -i" ``` ## Thien-Thi Nguyen, 2008-01-02 11:48 Subject: Re: reflog weirdness Message-ID: <873atgqwhm.fsf@ambire.localdomain> URL: https://gitlist.dev/e/873atgqwhm.fsf%40ambire.localdomain In-Reply-To: <7vprwqcqk3.fsf@gitster.siamese.dyndns.org> ``` () Junio C Hamano () Fri, 28 Dec 2007 16:06:36 -0800 "git-rebase -i" thanks. works great. thi ```