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

Re: cvs importer woes

From
Andreas Ericsson <ae@op5.se>
Date
Jun 27, 2006, 10:49 UTC
Message-ID
<44A10D47.3060708@op5.se>
In-Reply-To
<46a038f90606270342k2288cc2ds34ae05e089b8c906@mail.gmail.com>
Martin Langhoff wrote:
Show 11 quoted lines
> On 6/27/06, Andreas Ericsson <ae@op5.se> wrote:
> 
>> Sadly, the cvsimport command no longer works to create new repositories
>> from scratch.
> 
> 
> We are seeing some breakage in cvsimport that started with a patch of mine:
> 
> 8f732649bc4d5619a1b399e5808b3f4c662ad200 cvsimport: keep one index
> per branch during import
> 

I experimented a bit with that one too, but it worked for my (very small, no branches, no tags) cvs repo

Show 10 quoted lines
> 
>> The culprit is definitely 061303f0b50a648db8e0af23791fc56181f6bf93.
>>
>> Any perl-literate takers? Otherwise, just reverting the patch makes
>> things work (for me) again.
> 
> 
> Don't just revert that patch, unless I'm wrong there is some subtle
> branch-creation breakage too.
> 
Dscho's patch on top of 061303f0b works wonders. Thanks all the same though.
-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Previous: Martin Langhoff
Message 7 of 7 in “cvs importer woes”
  1. Andreas EricssonJun 27, 2006
  2. [TRYTHIS] cvsimport: fix initial importJohannes Schindelin, Jun 27, 2006
  3. Andreas EricssonJun 27, 2006
  4. Martin LanghoffJun 27, 2006
  5. Johannes SchindelinJun 27, 2006
  6. Martin LanghoffJun 27, 2006
  7. Andreas EricssonJun 27, 2006

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.