From: esr@thyrsus.com (Eric S. Raymond)
To: emacs-devel@gnu.org
Subject: git conversion trial repository #5
Date: Thu, 15 May 2014 04:38:17 -0400 (EDT) [thread overview]
Message-ID: <20140515083817.3E5A1380391@snark.thyrsus.com> (raw)
Next review version of the repository conversion is here:
git@gitorious.org:emacs-transition/review5.git
This one is current to complete to 2014-05-14 17:55:37 +0400.
It has been repacked.
Cloning this may appear at first site to fetch only the master branch,
but do "git branch -a" to list the other remote branches. You can
easily create local tracking branches for those you are interested in.
The conversion machinery, including the lift script, can be cloned from
git@gitorious.org:emacs-transition/emacs-transition.git
How you can help:
1. Report Bazaar and CVS references that aren't already in the
emacs.lift file (see BAZAAR REFERENCES and CVS REFERENCES).
2. Check the CVS references already in emacs.lift (see CVS REFERENCES).
3. Check bzr references translated with nochecklog, nocheckcomment,
everylog, and everycomment. (The changelog and changecomment commands
do not need to be checked by hand as they are automatically verified
by a script in the conversion machinery.)
4. Use gitk or git log to spot CVS cliques consisting of uncoalesced
single-file changes and their ChangeLog entry commits; report them so
I can squash them into proper changesets.
5. Investigate the old-branches and other-branches groups and determine
which branches, if any, should be discarded.
6. (Advanced) Identify the actual deletion points of as many of the
=-prefixed attic files as possible. Look for the string "ATTIC
FILES" in emacs.lift and try to turn 'attic' calls into 'deattic'
calls. (I've already done this, but it's a difficult and finicky process;
I might have missed some.)
7. (Advanced) Learn the reposurgeon DSL. Use this knowledge to audit
emacs.lift for correctness.
Barring any glitches found by people (other than me) doing these
auditing steps, the conversion procedure is pretty much ready to go.
I rerun it occasionally to catch new bzr references in the logs and
comments. Note that a full conversion takes about eight hours of
commpute time; this constraint needs to be planned around in the
conversion-day schedule.
A couple of work items remain on my list for after 24.4 release and
before the conversion, most notably merging and testing Rüdiger
Sonderfeld's improvement for vc.el.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Americans have the will to resist because you have weapons.
If you don't have a gun, freedom of speech has no power.
-- Yoshimi Ishikawa, Japanese author, in the LA Times 15 Oct 1992
next reply other threads:[~2014-05-15 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 8:38 Eric S. Raymond [this message]
2014-05-15 15:57 ` git conversion trial repository #5 Paul Eggert
2014-05-15 16:03 ` David Kastrup
2014-05-15 17:14 ` Eric S. Raymond
2014-05-15 17:24 ` Geoff Shannon
2014-05-15 17:45 ` Eli Zaretskii
2014-05-15 18:09 ` Eric S. Raymond
2014-05-15 20:20 ` Glenn Morris
2014-05-15 20:25 ` Eric S. Raymond
2014-05-18 16:18 ` Rüdiger Sonderfeld
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=20140515083817.3E5A1380391@snark.thyrsus.com \
--to=esr@thyrsus.com \
--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).