git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: Computing the number of patches in linux-next tree

From
Luck, Tony <tony.luck@intel.com>
Date
Jul 22, 2008, 17:13 UTC
Message-ID
<57C9024A16AD2D4C97DC78E552063EA306640DDC@orsmsx505.amr.corp.intel.com>
In-Reply-To
<7vabg9n93f.fsf@gitster.siamese.dyndns.org>
Show 7 quoted lines
>> 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.

Using git merge-base on the next-20080701 tag and current Linus tree I get 76 possible merge bases. None of them appear to be the "right" one (if I check out this tag and look at Next/merge.log the right answer appears to be 1702b52 if I'm reading the log correctly).

Perhaps my best hope is to
        $ git checkout $tag Next/merge.log
        ... parse merge.log to figure out $base ...
-Tony
Previous: Junio C HamanoNext: Johannes Schindelin
Message 4 of 6 in “Computing the number of patches in linux-next tree”
  1. Tony LuckJul 22, 2008
  2. Johannes SchindelinJul 22, 2008
  3. Junio C HamanoJul 22, 2008
  4. Luck, TonyJul 22, 2008
  5. Johannes SchindelinJul 22, 2008
  6. Harvey HarrisonJul 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.