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

Re: Fwd: git cvsimport implications

From
Junio C Hamano <gitster@pobox.com>
Date
May 14, 2013, 22:19 UTC
Message-ID
<7vfvxpfbli.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAPZPVFZLDwLNazvBh5n=Jg_=CZUNz3yTme4JW2NutPgjPzwtLg@mail.gmail.com>
Eugene Sajine <euguess@gmail.com> writes:
> What if there are a lot of branches in the CVS repo? Is it guaranteed
> to be broken after import?

Even though CVS repository can record branches in individual ,v files, reconstructing per branch history and where the branch happened in each "changeset" cannot be determined with any certainty. The best you can get is a heuristic result.

I do not think anybody can give such a guarantee. The best you can do is to convert it and validate if the result matches what you think has happened in the CVS history.

Previous: Eugene SajineNext: Michael Haggerty
Message 2 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.