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

Re: CVS <--> GIT workflow...

From
DCDavid Chanters <david.chanters@googlemail.com>
Date
Jul 1, 2009, 19:29 UTC
Message-ID
<ac3d41850907011229w34e9260akde8cad5f4ce0749b@mail.gmail.com>
In-Reply-To
<43d8ce650907011224l52910844wb13df2ab1d87dea5@mail.gmail.com>
2009/7/1 John Tapsell <johnflux@gmail.com>:
Show 9 quoted lines
> 2009/7/1 David Chanters <david.chanters@googlemail.com>:
>> Hi all,
>> for
>> a variety of reasons we're unable to simply switch away from using CVS
>> to Git.
>
> Perhaps you could switch from CVS to SVN?  SVN improves on CVS but
> behaves in a very similar way.  Then you can use the mature git-svn
> tool.

I wish, but this isn't feasible. I'd rather not have to go into details as to why, but suffice it to say, I am stuck with CVS for now -- changing to anything else, even SVN, is not an option, alas.

David
Previous: John TapsellNext: Jakub Narebski
Message 3 of 6 in “CVS <--> GIT workflow...”
  1. David ChantersJul 1, 2009
  2. John TapsellJul 1, 2009
  3. David ChantersJul 1, 2009
  4. Jakub NarebskiJul 1, 2009
  5. David ChantersJul 1, 2009
  6. Nick WoolleyJul 2, 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.