Re: [PATCH 2/4] merge-base: "--is-ancestor A B"

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 31, 2012, 18:45 UTC
Message-ID: <7v3932oq7z.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CANiSa6i5tY_V_dhK0wSaKzy0xwvN9uTqRJUJ7ZvgqCG7Ta5rsQ@mail.gmail.com>

Martin von Zweigbergk <martinvonz@gmail.com> writes:

Show 15 quoted lines

> On Fri, Aug 31, 2012 at 10:25 AM, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> I think "merge-base -h" will get this for free thanks to parseopt.
>
> It seems not, or maybe I'm using the wrong terminology; I meant to
> include it in the first part of the below.
>
> usage: git merge-base [-a|--all] <commit> <commit>...
>    or: git merge-base [-a|--all] --octopus <commit>...
>    or: git merge-base --independent <commit>...
>
>     -a, --all             output all common ancestors
>     --octopus             find ancestors for a single n-way merge
>     --independent         list revs not reachable from others
>     --is-ancestor         is the first one ancestor of the other?

Ahh.

As most of the modern parse-optified ones just say "git cmd <args>" or something like that, I wasn't paying attention to the upper part.

Will amend again.  Thanks.