From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [BUG] Empty reflogs and "git log -g"
Date: Thu, 08 Feb 2007 20:37:44 +0100 [thread overview]
Message-ID: <eqfu36$lb3$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0702082021210.22628@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Thu, 8 Feb 2007, Santi Béjar wrote:
>
>> when a reflog entry do not have a reflog message the refs@{num} syntax
>> gives a different result than with 'git log -g'. Actually 'git log -g'
>> just skips this ref.
>
> I could be that some older git version produces empty messages. But I'd
> regard the empty messages to be the problem. Or is the current Git version
> still producing such entries?
StGIT used to produce no reflog messages; I don't know if this has improved.
But you can have old reflog entries with empty messages; git log -g should
deal with them IMHO.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-08 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 1:21 [BUG] Empty reflogs and "git log -g" Santi Béjar
2007-02-08 7:25 ` Santi Béjar
2007-02-08 19:36 ` Johannes Schindelin
2007-02-08 19:49 ` Nicolas Pitre
2007-02-08 20:02 ` Johannes Schindelin
2007-02-08 19:22 ` Johannes Schindelin
2007-02-08 19:37 ` Jakub Narebski [this message]
2007-02-08 19:46 ` Johannes Schindelin
2007-02-08 23:18 ` Junio C Hamano
2007-02-08 23:59 ` [PATCH] for_each_reflog_ent: be forgiving about missing message Johannes Schindelin
2007-02-09 0:28 ` [PATCH] log --reflog: use dwim_log Johannes Schindelin
2007-02-09 3:43 ` Junio C Hamano
2007-02-09 7:19 ` Junio C Hamano
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='eqfu36$lb3$1@sea.gmane.org' \
--to=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.