From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Thibault Kruse <tibokruse@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: git branch -v output ambiguous for parser
Date: Thu, 23 Jul 2015 15:44:34 +0200 [thread overview]
Message-ID: <1437659074.25048.11.camel@kaarsemaker.net> (raw)
In-Reply-To: <CAByu6UVzsoK=OHkYv_zBCYf2YnBqx268TZ+_pi98N6pMt_NSgw@mail.gmail.com>
On do, 2015-07-23 at 15:29 +0200, Thibault Kruse wrote:
> Hi,
>
> trying to write a git wrapper, I wanted to parse the output of git branch -v
The output of git branch is not meant to be machine-parsed. Try using
git for-each-ref :)
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
prev parent reply other threads:[~2015-07-23 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 13:29 git branch -v output ambiguous for parser Thibault Kruse
2015-07-23 13:44 ` Dennis Kaarsemaker [this message]
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=1437659074.25048.11.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
--cc=tibokruse@googlemail.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).