From: Mike McCormack <mike@codeweavers.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Planning a git-cvsdaemon
Date: Mon, 12 Dec 2005 05:57:11 +0900 [thread overview]
Message-ID: <439C92A7.4030704@codeweavers.com> (raw)
In-Reply-To: <46a038f90512101844q326b3d43nf8b40617bd82c576@mail.gmail.com>
Martin Langhoff wrote:
> 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
prev parent reply other threads:[~2005-12-11 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 2:44 [RFC] Planning a git-cvsdaemon Martin Langhoff
2005-12-11 20:57 ` Mike McCormack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=439C92A7.4030704@codeweavers.com \
--to=mike@codeweavers.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).