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

git-svn.perl - bug in lookup_svn_merge()

From
ebik <ebik@ucw.cz>
Date
Oct 9, 2010, 09:20 UTC
Message-ID
<20101009112016.3e3ed175@Chewbacca.cub>

I triggered a bug in lookup_svn_merge when I was trying to convert one of our repositories.

Namely the $bottom variable has sometimes value '1', i.e. the first commit ever. Then it pushes "$bottom_commit^..$top_commit" to some list for further processing. This processing fails, because there is no commit before the first one.

We should test existence of parent of $bottom_commit, but I don't know what is the correct behavior if it does not exist.

-- 
                                 Tomáš 'ebík' Ebenlendr
                                 PF 2010.77113540081
Message 1 of 1 in “git-svn.perl - bug in lookup_svn_merge()”
  1. ebikOct 9, 2010

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.