unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: esr@thyrsus.com
Cc: lekktu@gmail.com, Alan Mackenzie <acm@muc.de>,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: use git, not cvs
Date: Tue, 10 Jun 2008 12:36:55 +0200	[thread overview]
Message-ID: <878wxd1sqg.fsf_-_@rho.meyering.net> (raw)
In-Reply-To: <20080607193747.GB1420@thyrsus.com> (Eric S. Raymond's message of "Sat, 7 Jun 2008 15:37:47 -0400")

"Eric S. Raymond" <esr@thyrsus.com> wrote:
...
> Well, that's one way to put it.  An equally valid analysis would
> be that -d ought to be the default rather than an option I've
> never heard of before, and CVS is broken as designed.

FYI, you can dump cvs and use git instead.
At least for emacs, you *can* do that.
I've been syncing a read-only git mirror to the CVS repository
for many months, so you can "checkout" a copy like this:

    git clone git://git.sv.gnu.org/emacs

The git repository should never be more than about 30-60
minutes behind the CVS one.

Preparing change-sets in git and pushing them back to
the cvs repository is not as painful as you might imagine,
thanks to the "git cvsexportcommit" command.  With a couple
of simple wrapper scripts and a little easy-to-manage local
policy, you might even come to find it "easy".




  parent reply	other threads:[~2008-06-10 10:36 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080607125159.8A74F9F05B4@grelber.thyrsus.com>
2008-06-07 13:20 ` Emacs-devel Digest, Vol 52, Issue 61 Eric S. Raymond
2008-06-07 14:14   ` Alan Mackenzie
2008-06-07 14:07     ` Juanma Barranquero
2008-06-07 15:24       ` Alan Mackenzie
2008-06-07 15:29         ` Juanma Barranquero
2008-06-07 16:46         ` Eli Zaretskii
2008-06-07 18:34           ` Alan Mackenzie
2008-06-07 19:39             ` Eric S. Raymond
2008-06-07 19:53             ` Glenn Morris
2008-06-07 20:10               ` Eric S. Raymond
2008-06-07 20:53                 ` Eli Zaretskii
2008-06-07 21:12                   ` Eric S. Raymond
2008-06-08  2:49                   ` Stefan Monnier
2008-06-07 21:26                 ` Alan Mackenzie
2008-06-07 21:13                   ` Eric S. Raymond
2008-06-08  8:21                 ` Richard M Stallman
2008-06-07 21:15               ` Alan Mackenzie
2008-06-07 19:37           ` Eric S. Raymond
2008-06-07 19:40             ` David Kastrup
2008-06-07 22:14             ` Nick Roberts
2008-06-07 22:42               ` joakim
2008-06-07 22:47               ` David Kastrup
2008-06-08  2:46             ` Stefan Monnier
2008-06-08  2:50               ` Miles Bader
2008-06-10 10:36             ` Jim Meyering [this message]
2008-06-10 10:42               ` use git, not cvs Juanma Barranquero
2008-06-10 11:00                 ` Jim Meyering
2008-06-10 11:02                   ` Juanma Barranquero
2008-06-10 11:08               ` Miles Bader
2008-06-10 11:16                 ` Juanma Barranquero
2008-06-10 11:27                   ` Miles Bader
2008-06-10 11:30                     ` Juanma Barranquero
2008-06-10 11:34                     ` Jim Meyering
2008-06-10 11:20                 ` Jim Meyering
2008-06-10 11:26                   ` Nick Roberts
2008-06-10 14:33                 ` Stefan Monnier
2008-06-07 19:35       ` Emacs-devel Digest, Vol 52, Issue 61 Eric S. Raymond
2008-06-07 14:20   ` Chong Yidong
2008-06-07 14:23   ` Miles Bader
2008-06-07 19:41     ` Eric S. Raymond
2008-06-07 20:28       ` Eli Zaretskii
2008-06-08  0:50     ` Stephen J. Turnbull
2008-06-08  0:42       ` David Kastrup
2008-06-07 14:26   ` Eli Zaretskii
2008-06-07 19:55     ` Eric S. Raymond
2008-06-07 20:52       ` Eli Zaretskii
2008-06-07 21:26         ` Eric S. Raymond
2008-06-07 22:52           ` Thomas Lord
2008-06-08  0:58             ` Stephen J. Turnbull

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878wxd1sqg.fsf_-_@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=lekktu@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).