From: Simo Melenius <simo.melenius@iki.fi>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug? "git branch" failing to list all branches
Date: Thu, 3 Jun 2010 09:00:14 +0300 [thread overview]
Message-ID: <AANLkTinCNgsIf_MsiysfphKm3MCW2Uio_xiemfDZraH7@mail.gmail.com> (raw)
In-Reply-To: <20100603042218.GA21254@progeny.tock>
On 3 June 2010 07:22, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> I noticed this because "git branch -a" and "git branch -av"
>> unexpectedly gave a very different output.
> Hmm --- so the error message must not have been very visible...
I have been working with such set of repositories that most of them
have one or two broken refs. I probably saw it but didn't care because
it was a known issue. If I had called git branch from a script and
piped the output somewhere while relying on exit status, I wouldn't
have noticed anything.
> Will this make ‘git branch’ exit with status zero? Scripts and people
> with fancy prompts benefit from a nonzero exit status.
My change doesn't change the current behaviour. At least git 1.7.0.4
didn't give a nonzero exit status either. It would be good if it did.
I could add that to my patch. I'm, however, unsure of what's the best
way to communicate the error from append_ref() to cmd_branch(). A
static variable in branch.c would of course do.
However, if the git codebase has somewhere a global mechanism for
signalling errors by, for example, raising some flag when error() is
called, using that mechanism would be better, right?
> If I have 37 branches and an error is encountered looking up one of
> them, with this patch the error message will scroll off the screen.
> Is this worth worrying about? It depends on what the usual causes for
> broken branch refs are and whether they require attention or can be
> safely ignored.
Since this only concerns the printing of branches, often for
interactive viewing or bash completion, and does not affect any of the
operations that modify the repository, I think it's sufficient that
the error message is still readable from stderr for those who are
interested.
> One other thought: this patch is line-wrapped, which means it cannot
> be mechanically applied. Documentation/SubmittingPatches has some
> tips on sending a patch unmangled (and please also see the section
> labelled "Sign your work").
Yeah, I have a kosher patch locally. I just copypasted the diff part
here for discussion.
Simo
--
() Today is the car of the cdr of your life.
/\ http://arc.pasp.de/
next prev parent reply other threads:[~2010-06-03 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 14:47 Bug? "git branch" failing to list all branches Simo Melenius
2010-06-03 4:22 ` Jonathan Nieder
2010-06-03 6:00 ` Simo Melenius [this message]
2010-06-03 6:55 ` Jonathan Nieder
2010-06-03 7:48 ` [PATCH 1/2] branch: exit status now reflects if branch listing finds an error Simo Melenius
2010-06-04 2:24 ` Jonathan Nieder
2010-06-03 7:48 ` [PATCH 2/2] branch: don't fail listing branches if one of the commits wasn't found Simo Melenius
2010-06-03 17:42 ` Sverre Rabbelier
2010-06-04 2:43 ` Jonathan Nieder
2010-06-04 9:48 ` Simo Melenius
2010-06-04 9:50 ` [PATCH 1/2] branch: exit status now reflects if branch listing finds an error Simo Melenius
2010-06-04 9:50 ` [PATCH 2/2] branch: don't fail listing branches if one of the commits wasn't found Simo Melenius
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=AANLkTinCNgsIf_MsiysfphKm3MCW2Uio_xiemfDZraH7@mail.gmail.com \
--to=simo.melenius@iki.fi \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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).