From: Pavel Roskin <proski@gnu.org>
To: Jim Meyering <jim@meyering.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: synchronizing incremental git changes to cvs
Date: Mon, 22 May 2006 12:29:22 -0400 [thread overview]
Message-ID: <1148315362.29228.27.camel@dv> (raw)
In-Reply-To: <873bf3jy2t.fsf@rho.meyering.net>
Hello, Jim!
On Sun, 2006-05-21 at 15:40 +0200, Jim Meyering wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Sun, 21 May 2006, Jim Meyering wrote:
> >
> >> Why am I interested? I want to switch the development of GNU coreutils
> >> from cvs to git.
I believe you have a very good reason to talk to decision makers in FSF.
Savannah is very poorly maintained, and I actually took one of my
projects (Orinoco driver) to SourceForge Subversion.
If losing a Linux driver is next to nothing, losing GNU coreutils is a
big deal for the GNU development site. You are likely to be heard if
you request git support.
> I would also like to continue making the repository
> >> available via cvs, for the sake of continuity. At worst, I can always
> >> cut the CVS cord, but that's a last resort.
Subversion is as easy as CVS for potential users, but it has a useful
"log" command if nothing else. It also have real changesets, which
means no more guesswork when moving changes back and forth.
> > If you only want to make a cvs repository available for tracking the
> > project, git-cvsserver is what you want. It is even faster than the
> > original cvs...
>
> That might work if I had sufficient access to the system hosting the
> public CVS repository. But there are restrictions (like no ssh access).
> Currently I rsync the master repo to an intermediate site, from which
> it is periodically pulled by savannah. Paranoia on both sides.
>
> If I end up leaving savannah, can someone propose a good site,
> i.e., secure, yet with git and rsync access?
Sorry, I don't know any free git hosters, but here's what you can do:
1) Pressure Savannah to support git
2) Use arch on Savannah
3) Move to Subversion on SourceForge, GNA.org or Berlios and use git-svn
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-05-22 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 22:13 synchronizing incremental git changes to cvs Jim Meyering
2006-05-20 23:05 ` Johannes Schindelin
2006-05-21 13:40 ` Jim Meyering
2006-05-22 16:29 ` Pavel Roskin [this message]
2006-05-22 17:05 ` Jakub Narebski
2006-05-21 0:09 ` Martin Langhoff
2006-05-21 16:37 ` Jim Meyering
2006-05-21 18:21 ` Junio C Hamano
2006-05-21 21:31 ` Jim Meyering
2006-05-21 21:35 ` don't accept bogus N in `HEAD~N' Jim Meyering
2006-05-21 21:42 ` Jakub Narebski
2006-05-22 7:38 ` Jim Meyering
2006-05-22 8:16 ` Junio C Hamano
2006-05-22 8:25 ` Junio C Hamano
2006-05-22 6:57 ` avoid atoi, when possible; int overflow -> heap corruption Jim Meyering
2006-05-22 13:16 ` Morten Welinder
2006-05-22 13:31 ` Jim Meyering
2006-05-22 13:37 ` Jeff King
2006-05-22 13:54 ` Morten Welinder
2006-05-22 10:27 ` detect write failure, even for stdout Jim Meyering
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=1148315362.29228.27.camel@dv \
--to=proski@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
/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).