From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Funny reflog has missing space
Date: Tue, 27 Feb 2007 12:32:39 -0800 [thread overview]
Message-ID: <7vslcrcpeg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v4pp7flew.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Tue, 27 Feb 2007 11:30:31 -0800")
Junio C Hamano <junkio@cox.net> writes:
> Andy Parkins <andyparkins@gmail.com> writes:
>
>> Hello,
>>
>> I've just peeked in my reflog (tail .git/logs/HEAD), and found something
>> strange:
>>
>> 72160ca5c05fab4fbd3c24c9b13cbd0651b60532
>> ca7b20e2677960cfc52c525b8f8bdf12ce79176b Andy Parkins <long@emailaddress.com>
>> 1172589175 +0000commit: Log message goes here
>>
>> Notice that there is no space between the "+0000" and the "commit".
>> ...
>> Is this normal? "git-reflog show" works fine in both cases.
>
> It is not. It would be good to find out who puts corrupted
> entry.
Hmmm. I am puzzled. The only two low-level locations I know of
that writes into reflog are:
* builtin-reflog.c::expire_reflog_ent() copies existing log
entry, which are parsed out, after reformatting it. It has
an explicit "\t" in the format string, so it is not it.
* refs.c::log_ref_write() gets an optional log message and
writes it after the GMT offset, with an explicit "\t", so
this is not it, either.
next prev parent reply other threads:[~2007-02-27 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:29 Funny reflog has missing space Andy Parkins
2007-02-27 15:59 ` Johannes Schindelin
2007-02-27 19:30 ` Junio C Hamano
2007-02-27 20:32 ` Junio C Hamano [this message]
2007-02-28 9:34 ` OT: Funny tab behaviour on terminals Andy Parkins
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=7vslcrcpeg.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).