From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: reflog weirdness
Date: Fri, 28 Dec 2007 22:35:33 +0100 [thread overview]
Message-ID: <87prwqec4a.fsf@ambire.localdomain> (raw)
In-Reply-To: <7vhci2ectr.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 28 Dec 2007 13:20:16 -0800")
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
() 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:
[-- Attachment #2: top of \"git show\" output --]
[-- Type: application/octet-stream, Size: 257 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
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
next prev parent reply other threads:[~2007-12-28 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 19:57 reflog weirdness Thien-Thi Nguyen
2007-12-28 21:20 ` Junio C Hamano
2007-12-28 21:35 ` Thien-Thi Nguyen [this message]
2007-12-28 22:01 ` Junio C Hamano
2007-12-28 22:44 ` Thien-Thi Nguyen
2007-12-29 0:06 ` Junio C Hamano
2008-01-02 11:48 ` Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prwqec4a.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox