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

CVS <--> GIT workflow...

From
DCDavid Chanters <david.chanters@googlemail.com>
Date
Jul 1, 2009, 18:32 UTC
Message-ID
<ac3d41850907011132q8e19b37ofa10813258a97555@mail.gmail.com>
Hi all,
[ Please Cc me, as I am not subscribed to the list. ]

I am wondering if there's any best practises/howtos on using CVS and Git together. I have a project which is currently residing in CVS; people actively use it to add changes, etc. Which is fine -- and for a variety of reasons we're unable to simply switch away from using CVS to Git.

So... the question is, can I use Git locally to manage all my work in -- create topic branches, merge them, etc., and then commit that back out to the CVS repository? Likewise, I would need to keep my Git repository in synch with any changes to the CVS repository -- is that possible? Has anyone else done something like this? What I am effectively wanting to do is Git for my entire development on this project and just forget it even uses CVS.

I've read up on git-cvsimport which seems to explain how to convert a current CVS repo over to Git -- is that right? Any information you can point me to would be very welcome. I am not adverse to reading, providing it's useful to me. :)

Thanks, in advance,
David
Next: John Tapsell
Message 1 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.