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

Re: [RFC] Planning a git-cvsdaemon

From
MMMike McCormack <mike@codeweavers.com>
Date
Dec 11, 2005, 20:57 UTC
Message-ID
<439C92A7.4030704@codeweavers.com>
In-Reply-To
<46a038f90512101844q326b3d43nf8b40617bd82c576@mail.gmail.com>
Martin Langhoff wrote:
Show 6 quoted lines
> In any case, I am after feedback in general (and any truly
> insurmountable issues you can think of),  I haven't found yet  a good
> library implementing the server side of the protocol (other than
> cvs's). git-cvsdaemon will probably take shape in Perl initially,
> though if there's a good cvs protocol library in other scripting
> language, I'm interested...
Hey Martin,
That's a neat idea, and a great way to get projects to move from CVS to GIT.

I'd recommend that you avoid providing commit access to a GIT repository via CVS for starters. Many projects (eg. Wine) would benefit greatly from just having a way for people to get the source via CVS without having to write scripts to maintain a CVS tree in parallel. Serious developers will use GIT if the master repository is GIT anyway.

Mike
Previous: Martin Langhoff
Message 2 of 2 in “[RFC] Planning a git-cvsdaemon”
  1. Martin LanghoffDec 11, 2005
  2. Mike McCormackDec 11, 2005

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.