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

Re: Fwd: git cvsimport implications

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
May 17, 2013, 09:10 UTC
Message-ID
<5195F3EB.8000308@alum.mit.edu>
In-Reply-To
<CAPZPVFZTZFQrCF3gcwcff5LFm9MHhZm-DauLvfzCYrMTw4nQfA@mail.gmail.com>
On 05/15/2013 08:03 PM, Eugene Sajine wrote:
Show 5 quoted lines
> My primary goal was to understand better what are the real problems
> that we might have with the way we use git cvsimport, so I was not
> asking about the guarantee of the cvsimport to import things
> correctly, but if there is a guarantee the import will result in
> completely broken history.

So what are you going to do, use cvsimport whenever you cannot *prove* that it is wrong? You sure have low standards for your software.

The only *useful* guarantee is that software is *correct* under defined circumstances. I don't think anybody has gone to the trouble to figure out when that claim can be made for cvsimport.

> If the cvsimport is that broken - is there any plan to fix it?

For one-time imports, the fix is to use a tool that is not broken, like cvs2git.

Alternatively, Eric Raymond claims to have developed a new version of cvsps that is not quite as broken as the old version. Presumably cvsimport would be not quite as broken if used with the new cvsps.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Eugene SajineNext: John Keeping
Message 5 of 13 in “Fwd: git cvsimport implications”
  1. Eugene SajineMay 14, 2013
  2. Junio C HamanoMay 14, 2013
  3. Michael HaggertyMay 15, 2013
  4. Eugene SajineMay 15, 2013
  5. Michael HaggertyMay 17, 2013
  6. John KeepingMay 17, 2013
  7. Martin LanghoffMay 17, 2013
  8. Michael HaggertyMay 17, 2013
  9. Andreas KreyMay 17, 2013
  10. Martin LanghoffMay 17, 2013
  11. Michael HaggertyMay 17, 2013
  12. Fwd: Fwd: git cvsimport implicationsEugene Sajine, May 17, 2013
  13. Michael HaggertyMay 18, 2013

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.