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

Re: [PATCH 0/3] git-svn: Handle git root commits in mergeinfo ranges

From
EWEric Wong <normalperson@yhbt.net>
Date
Jun 28, 2011, 03:37 UTC
Message-ID
<20110628033732.GA14132@dcvr.yhbt.net>
In-Reply-To
<1308379680-17188-1-git-send-email-mhagger@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> wrote:
> I don't believe the extra "git rev-parse" invocation to be a
> performance problem, but I am not familiar enough with the code to be
> certain.

It shouldn't be a problem. Sam Vilain did all the merge tracking code, but this looks entirely reasonable.

> Michael Haggerty (3):
>   git-svn: Demonstrate a bug with root commits in mergeinfo ranges
>   git-svn: Disambiguate rev-list arguments to improve error message
>   git-svn: Correctly handle root commits in mergeinfo ranges
Thanks Michael.

All acked and pushed to "master" for Junio at git://bogomips.org/git-svn These should go to maint, too.

-- 
Eric Wong
Previous: Michael Haggerty
Message 5 of 5 in “git-svn: Handle git root commits in mergeinfo ranges”
  1. 0/3 git-svn: Handle git root commits in mergeinfo rangesMichael Haggerty, Jun 18, 2011
  2. 1/3 git-svn: Demonstrate a bug with root commits in mergeinfo rangesMichael Haggerty, Jun 18, 2011
  3. 2/3 git-svn: Disambiguate rev-list arguments to improve error messageMichael Haggerty, Jun 18, 2011
  4. 3/3 git-svn: Correctly handle root commits in mergeinfo rangesMichael Haggerty, Jun 18, 2011
  5. Eric WongJun 28, 2011

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.