From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Tony Luck <tony.luck@intel.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Computing the number of patches in linux-next tree
Date: Tue, 22 Jul 2008 10:04:52 -0700 [thread overview]
Message-ID: <7vabg9n93f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807221727210.8986@racer> (Johannes Schindelin's message of "Tue, 22 Jul 2008 17:28:17 +0100 (BST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 22 Jul 2008, Tony Luck wrote:
>
>> git tag | grep next- | sort | while read tag
>
> This should not be necessary... AFAICT "git tag" sorts its output already.
>
>> What does the "git-where-did-this-tag-branch-from-linus" command look like?
>
> git merge-base --all <branch1> <branch2>
>
> Be warned: there might be multiple merge bases.
I do not think that approach applies to linux-next, which is constantly
rewound to the then-tip-of-linus and merge remaining bits. The question
is "where does this branch begin", which does not have an answer in git.
next prev parent reply other threads:[~2008-07-22 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 16:19 Computing the number of patches in linux-next tree Tony Luck
2008-07-22 16:28 ` Johannes Schindelin
2008-07-22 17:04 ` Junio C Hamano [this message]
2008-07-22 17:13 ` Luck, Tony
2008-07-22 17:24 ` Johannes Schindelin
2008-07-22 18:23 ` Harvey Harrison
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=7vabg9n93f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tony.luck@intel.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).