From: "Eric S. Raymond" <esr@thyrsus.com>
To: David Kastrup <dak@gnu.org>
Cc: 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 11:23:53 -0500 [thread overview]
Message-ID: <20140116162353.GA17303@thyrsus.com> (raw)
In-Reply-To: <87ha940x1y.fsf@fencepost.gnu.org>
David Kastrup <dak@gnu.org>:
> > Wow. That's a record; I've never actually seen more than three
> > transitions before. I will correct.
>
> Emacs is at the forefront of everything.
Or hindfront, or something. RCS. That's...impressive.
Most of the venerably ancient project histories I've converted only
have the following geological strata
1. Subversion
2. Random crap generated by cvs2svn
3. CVS
Layer 2 is the nasty one. Those conversion artifacts tend to trip up
Subversion-to-anything converters, especially git-svn. I originally
wrote reposurgeon to have a way to clean those up.
What I've never seen before is a plain RCS layer visible below the CVS
(now that I've been clued in some things in older ChangeLogs make sense.) I
guess that's because there just aren't that many projects old enough to
predate CVS. Only three out of over forty of mine are.
/me wouldn't be surprised to stumble over a fossil trilobite next.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2014-01-16 16:23 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 [this message]
2014-01-16 18:37 ` Paul Eggert
2014-01-16 20:01 ` Eric S. Raymond
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=20140116162353.GA17303@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dak@gnu.org \
--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).