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

Re: cvs import

From
Jon Smirl <jonsmirl@gmail.com>
Date
Sep 14, 2006, 16:27 UTC
Message-ID
<9e4733910609140927y30ecaa42wae0ff0597b8c3842@mail.gmail.com>
In-Reply-To
<eebuih$u32$1@sea.gmane.org>
On 9/14/06, Jakub Narebski <jnareb@gmail.com> wrote:
Show 6 quoted lines
> Shawn Pearce wrote:
>
> > Originally I wanted Jon Smirl to modify the cvs2svn (...)
>
> By the way, will cvs2git (modified cvs2svn) and git-fast-import publicly
> available?
It has some unresolved problems so I wasn't spreading it around everywhere.

It is based on cvs2svn from August. There has been too much change to the current cvs2svn to merge it anymore. It is going to need significant rewrite. But cvs2svn will all change again if it converts to the dependency model. It is better to get a backend independent interface build into cvs2svn.

It it not generating an accurate repo. cvs2svn is outputting tags based on multiple revisions, git can't do that. I'm just tossing some of the tag data that git can't handle. I base the tag on the fist revision which is not correct.

If the repo is missing branch tags cvs2svn may turn a single missing branch into hundreds of branches. The Mozilla repo has about 1000 extra branches because of this.

Sometime cvs2svn will partial copy from another rev to generate a new rev. Git doesn't do this so I am tossing the copy requests. I need to figure out how to hook into the data before cvs2svn tries to copy things.

cvs2svn makes no attempt to detect merges so gitk will show 1,700 active branches when there are really only 10 currently active branches in Mozilla.

That said 99.9% of Mozilla CVS is in the output git repo, but it isn't quite right.

If you still want the code I'll send it to you.
-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Shawn PearceNext: Michael Haggerty
Message 19 of 38 in “Re: cvs import”
  1. Jon SmirlSep 13, 2006
  2. Martin LanghoffSep 13, 2006
  3. Markus SchiltknechtSep 13, 2006
  4. Oswald BuddenhagenSep 13, 2006
  5. Martin LanghoffSep 13, 2006
  6. Michael HaggertySep 14, 2006
  7. Jon SmirlSep 14, 2006
  8. Michael HaggertySep 14, 2006
  9. Martin LanghoffSep 14, 2006
  10. Michael HaggertySep 14, 2006
  11. Jon SmirlSep 14, 2006
  12. Martin LanghoffSep 14, 2006
  13. Markus SchiltknechtSep 13, 2006
  14. Jon SmirlSep 13, 2006
  15. Michael HaggertySep 14, 2006
  16. Shawn PearceSep 14, 2006
  17. Jakub NarebskiSep 14, 2006
  18. Shawn PearceSep 14, 2006
  19. Jon SmirlSep 14, 2006
  20. Michael HaggertySep 14, 2006
  21. Jakub NarebskiSep 14, 2006
  22. Jon SmirlSep 14, 2006
  23. Markus SchiltknechtSep 15, 2006
  24. Shawn PearceSep 16, 2006
  25. Oswald BuddenhagenSep 16, 2006
  26. Nathaniel SmithSep 16, 2006
  27. Nathaniel SmithSep 13, 2006
  28. Daniel CarosoneSep 13, 2006
  29. Daniel CarosoneSep 13, 2006
  30. Keith PackardSep 13, 2006
  31. Nathaniel SmithSep 14, 2006
  32. Jon SmirlSep 14, 2006
  33. Daniel CarosoneSep 14, 2006
  34. Shawn PearceSep 14, 2006
  35. Daniel CarosoneSep 14, 2006
  36. Petr BaudisSep 14, 2006
  37. Shawn PearceSep 14, 2006
  38. Shawn PearceSep 14, 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.