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

RE: Best way to merge two repos with same content, different history

From
KHKelly F. Hickel <kfh@mqsoftware.com>
Date
Jun 5, 2009, 17:10 UTC
Message-ID
<63BEA5E623E09F4D92233FB12A9F794303117DC1@emailmn.mqsoftware.com>
In-Reply-To
<286817520906050953n1afed29cn6c85f219a0c9b8b5@mail.gmail.com>
Show 19 quoted lines
> -----Original Message-----
> From: Rostislav Svoboda [mailto:rostislav.svoboda@gmail.com]
> Sent: Friday, June 05, 2009 11:54 AM
> To: Kelly F. Hickel
> Cc: git@vger.kernel.org
> Subject: Re: Best way to merge two repos with same content, different
> history
> 
> On Fri, Jun 5, 2009 at 18:30, Kelly F. Hickel<kfh@mqsoftware.com>
> wrote:
> >        We're converting out of CVS after 10 years... The cvs2git
> > conversion takes around 4-5 days, and there doesn't seem to be any
> way
> > to speed that up.
> 
> try google:
> "cvs2git migration - cloning CVS repository"
> 
> Bost
Bost, 
	Thanks, but I'm already working with a local copy of the CVS repo.  I've corresponded with Michael Haggerty about the time this takes, and there just doesn't seem to be any way to improve the speed, without making some fairly drastic changes to cvs2git.

Thanks, Kelly

Previous: Rostislav SvobodaNext: Rostislav Svoboda
Message 3 of 12 in “Best way to merge two repos with same content, different history”
  1. Kelly F. HickelJun 5, 2009
  2. Rostislav SvobodaJun 5, 2009
  3. Kelly F. HickelJun 5, 2009
  4. Rostislav SvobodaJun 5, 2009
  5. Robin H. JohnsonJun 5, 2009
  6. Kelly F. HickelJun 5, 2009
  7. Robin H. JohnsonJun 5, 2009
  8. Kelly F. HickelJun 5, 2009
  9. Michael HaggertyJun 19, 2009
  10. Avery PennarunJun 5, 2009
  11. Kelly F. HickelJun 5, 2009
  12. Markus HeidelbergJun 5, 2009

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.