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

Re: [PATCH] cvstrack: work on imported cvs and other git branches

From
Steffen Prohaska <prohaska@zib.de>
Date
Jul 1, 2007, 19:52 UTC
Message-ID
<3599CEBD-F5AB-4DF6-BC00-372A9C710BEA@zib.de>
In-Reply-To
<Pine.LNX.4.64.0707011852531.4438@racer.site>
On Jul 1, 2007, at 7:53 PM, Johannes Schindelin wrote:
Show 10 quoted lines
> On Sun, 1 Jul 2007, Steffen Prohaska wrote:
>
>> The background is, I plan to convince approximately 60 developers
>> to migrate from CVS to git and I'm searching for a way to start the
>> transition with some beta testers, while maintaining full cvs
>> infrastructure in place for the remaining users.
>
> Why not just cvsimporting into git, and then replace the CVS server  
> with
> git-cvsserver? That's what I did.

I thought about that but I don't know yet how to slice our existing CVS repository. Most developers use partial checkouts.

But maybe I should reconsider and evaluate git-cvsserver in more detail.
	Steffen
Previous: Johannes Schindelin
Message 7 of 7 in “cvstrack: work on imported cvs and other git branches”
  1. cvstrack: work on imported cvs and other git branchesSteffen Prohaska, Jul 1, 2007
  2. Johannes SchindelinJul 1, 2007
  3. Steffen ProhaskaJul 1, 2007
  4. Johannes SchindelinJul 1, 2007
  5. Steffen ProhaskaJul 1, 2007
  6. Johannes SchindelinJul 1, 2007
  7. Steffen ProhaskaJul 1, 2007

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.