From: "Eric S. Raymond" <esr@thyrsus.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116038: On VCS-independent ways of identifying commits, and why they are desirable.
Date: Thu, 16 Jan 2014 15:01:21 -0500 [thread overview]
Message-ID: <20140116200121.GI17770@thyrsus.com> (raw)
In-Reply-To: <52D82705.6040507@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu>:
> On 01/16/2014 08:23 AM, Eric S. Raymond wrote:
>
> > there just aren't that many projects old enough to predate CVS.
>
> Hah! The last public software project I converted was from
> SCCS to Git. And this was genuine circa-1980 Programmer's
> Workbench SCCS, not some pale imitation. None of the
> repository converters I found on the web worked, so I had to
> write my own. I wish I'd known about your repository
> toolset -- maybe some of its Swiss Army knife blades would
> have saved me some work.
Quite likely. But if this was before 2010 reposurgeon didn't exist yet.
I maintain a Python version of sccs2rcs (yes, it's descended from the
C-shell version you know about). If I had to do SCCS -> git I would
run it and then lift the resulting RCS with cvs-fast-export (which
is a significantly improved version of the parsecvs code Keith
Packard wrote for lifting X).
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2014-01-16 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1W3frI-0000Fq-CC@vcs.savannah.gnu.org>
2014-01-16 14:45 ` [Emacs-diffs] trunk r116038: On VCS-independent ways of identifying commits, and why they are desirable Stefan Monnier
2014-01-16 15:00 ` Eric S. Raymond
2014-01-16 15:24 ` David Kastrup
2014-01-16 16:23 ` Eric S. Raymond
2014-01-16 18:37 ` Paul Eggert
2014-01-16 20:01 ` Eric S. Raymond [this message]
2014-01-16 16:34 ` Andreas Schwab
2014-01-16 17:32 ` Eric S. Raymond
2014-01-16 18:17 ` Andreas Schwab
2014-01-16 19:38 ` Eric S. Raymond
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=20140116200121.GI17770@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dak@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).