From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git log -g: Complain, but do not fail, when no reflogs are there
Date: Tue, 24 Jul 2007 12:17:23 +0200 [thread overview]
Message-ID: <81b0412b0707240317q56e42a9bs44eb3e5ef9e796c6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707241014500.14781@racer.site>
On 7/24/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Tue, 24 Jul 2007, Alex Riesen wrote:
> > On 7/24/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > >
> > > When asking "git log -g --all", clearly you want to see only those refs
> > > that do have reflogs, but you do not want it to fail, either.
> > >
> > > So instead of die()ing, complain about it, but move on to the other refs.
> > >
> >
> > I believe you wont even see these complaints: the pager will start shortly
> > afterwards and fill the screen with commits, completely hiding the errors.
>
> You can see it briefly, but it is hidden by default. Which is a good
> thing. If you set the pager to "cat" (which is happily not the default!)
> you can see them clearly. Until you are swamped by the rest of the
> output.
>
> Maybe this is a feature?
>
Maybe. I can't see it at all. Should I downgrade something or propose
a patch to put some delay after this error? I think not.
I think second Junios suggestion, but this is of course no
difference to me.
next prev parent reply other threads:[~2007-07-24 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 23:39 [PATCH] git log -g: Complain, but do not fail, when no reflogs are there Johannes Schindelin
2007-07-24 5:37 ` Junio C Hamano
2007-07-24 9:14 ` Johannes Schindelin
2007-07-24 7:26 ` Alex Riesen
2007-07-24 9:16 ` Johannes Schindelin
2007-07-24 10:17 ` Alex Riesen [this message]
2007-07-24 11:11 ` Johannes Schindelin
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=81b0412b0707240317q56e42a9bs44eb3e5ef9e796c6@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).