From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: historial question: the first commits (is the conversion screwed?)
Date: Sat, 17 Aug 2019 17:08:30 +0300 [thread overview]
Message-ID: <835zmvopep.fsf@gnu.org> (raw)
In-Reply-To: <878srrrk00.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 17 Aug 2019 15:37:03 +0200)
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Sat, 17 Aug 2019 15:37:03 +0200
>
> > revision 1.1
> > date: 1985-12-14 16:58:10 +0000; author: jimb; state: Exp;
> > Initial revision
>
>
> I see, the strange thing is that it seem the first file checkin was
> unused.el.
>
> I would have expected emacs.c or something like this.
You will have to ask Jim. I presume the initial commit was a long
process, one file at a time, and it was done according to some
more-or-less arbitrary order. Don't forget that Emacs was maintained
for several years before the initial commit, so all the files were
already there.
> The question is how reliable is the conversion? It seem to work
> reasonable well for the part which concerns bzr, but I am not so sure
> about the RCS stuff.
The result is consistent with what the CVS repository shows, so I
don't understand why you have any doubts.
next prev parent reply other threads:[~2019-08-17 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 11:02 historial question: the first commits (is the conversion screwed?) Uwe Brauer
2019-08-17 12:14 ` Eli Zaretskii
2019-08-17 12:18 ` Eli Zaretskii
2019-08-17 12:44 ` Eli Zaretskii
2019-08-17 13:37 ` Uwe Brauer
2019-08-17 14:08 ` Eli Zaretskii [this message]
2019-08-17 12:55 ` Stefan Monnier
2019-08-17 16:09 ` Uwe Brauer
2019-08-17 18:30 ` John Wiegley
2019-08-17 18:34 ` Uwe Brauer
2019-08-19 15:07 ` Jim Blandy
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=835zmvopep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).