emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New review conversion of Emacs repository


From: Eric S. Raymond
Subject: New review conversion of Emacs repository
Date: Sat, 13 Sep 2014 09:58:42 -0400 (EDT)

Next review version of the repository conversion is here:

        git://gitorious.org/emacs-transition/review6.git

This one is current to complete to 2014-09-11 12:44:25 -0700.
It has been repacked.

Cloning this may appear at first sight 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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]