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

Re: Change in cvsps maintainership, abd a --fast-export option

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Dec 21, 2012, 19:19 UTC
Message-ID
<50D4B639.9000807@alum.mit.edu>
In-Reply-To
<20121221104437.GA5244@thyrsus.com>
On 12/21/2012 11:44 AM, Eric S. Raymond wrote:
Show 10 quoted lines
> Michael Haggerty <mhagger@alum.mit.edu>:
>> If you haven't yet seen it, there is a writeup of the algorithm used by
>> cvs2git to infer the history of a CVS repository [1].  If your goal is
>> to make cvsps more robust, you might want to consider the ideas
>> described there.
> 
> I shall do so.  Their design ideas may well be interesting, even though I
> don't trust their code.  I've seem cvs2svn drop far too many weird artifacts 
> and just plain broken commits in the back history of Subversion repositories.
> I don't know if this is due to design problems, implementation bugs, or both.

If you have seen any problems with cvs2svn/cvs2git, please file bug reports. In the past years there have been very few valid bugs reported. We very often find that artifacts that users thought were bugs are in fact intentional workarounds required to make the contents of branches and tags in the target VCS agree with those in the CVS repository.

Perhaps your experience is with an older version of cvs2svn? If not, please be specific rather than just making complaints that are too vague to be rebutted or fixed (whichever is appropriate). I put a *lot* of effort into getting cvs2svn to run correctly, and I take bug reports very seriously.

Michael (the cvs2svn maintainer)

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Eric S. RaymondNext: Eric S. Raymond
Message 4 of 16 in “Change in cvsps maintainership, abd a --fast-export option”
  1. Eric S. RaymondDec 20, 2012
  2. Michael HaggertyDec 21, 2012
  3. Eric S. RaymondDec 21, 2012
  4. Michael HaggertyDec 21, 2012
  5. Eric S. RaymondDec 21, 2012
  6. Michael HaggertyDec 21, 2012
  7. Heiko VoigtDec 22, 2012
  8. Eric S. RaymondDec 22, 2012
  9. Heiko VoigtDec 22, 2012
  10. Eric S. RaymondDec 22, 2012
  11. Heiko VoigtDec 23, 2012
  12. Eric S. RaymondDec 22, 2012
  13. Antoine PelisseDec 22, 2012
  14. Eric S. RaymondDec 22, 2012
  15. Andreas SchwabDec 22, 2012
  16. Andreas SchwabDec 22, 2012

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.