From: John Keeping <john@keeping.me.uk>
To: Sergey Organov <sorganov@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, David Kastrup <dak@gnu.org>,
git@vger.kernel.org
Subject: Re: [BUG] Documentation: git log: --exit-code undocumented?
Date: Tue, 2 Dec 2014 12:27:05 +0000 [thread overview]
Message-ID: <20141202122705.GA22967@serenity.lan> (raw)
In-Reply-To: <87ppc2xp9k.fsf@osv.gnss.ru>
On Tue, Dec 02, 2014 at 02:30:31PM +0300, Sergey Organov wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > David Kastrup <dak@gnu.org> writes:
> >
> >> I disagree that --exit-code does nothing: it indicates whether the
> >> listed log is empty. So for example
> >>
> >> git log -1 --exit-code a..b > /dev/null
> >>
> >> can be used to figure out whether "a" is a proper ancestor of "b" or
> >> not.
> >
> > Hmph.
> >
> > $ git log --exit-code master..maint >/dev/null; echo $?
> > 0
> > $ git log --exit-code maint..master >/dev/null; echo $?
> > 1
> >
> > That is a strange way to use --exit-code.
>
> What's the best way then to tell if "a" is an ancestor of "b"?
git merge-base --is-ancestor a b
prev parent reply other threads:[~2014-12-02 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 11:50 [BUG] Documentation: git log: --exit-code undocumented? Sergey Organov
2014-12-01 16:29 ` Junio C Hamano
2014-12-01 16:32 ` Sergey Organov
2014-12-01 16:37 ` Junio C Hamano
2014-12-01 16:43 ` Sergey Organov
2014-12-01 17:32 ` David Kastrup
2014-12-01 17:49 ` Junio C Hamano
2014-12-01 18:30 ` David Kastrup
2014-12-02 11:30 ` Sergey Organov
2014-12-02 12:27 ` John Keeping [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=20141202122705.GA22967@serenity.lan \
--to=john@keeping.me.uk \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sorganov@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).