[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gnus update
Re: Gnus update
Tue, 27 Jul 2004 08:37:14 -0700
Miles Bader <address@hidden> writes:
> I think the best thing might be to have neither, but rather do two-way
> merging very frequently.
Is one of the Gnus maintainers an Emacs committer also? Perhaps the MH-E
model can be applied to Gnus.
Before each MH-E release, I run the import-emacs script (attached, but
specific to MH-E so read, understand, and modify accordingly before
using) which imports the current Emacs MH-E sources into the Emacs
branch in the MH-E CVS repository and then merges the changes into the
mainline (after I double-check them). I then release MH-E and then run
the install-emacs Makefile target which installs the MH-E files into
Emacs which are subsequently checked in.
Now, if I could create a single MH-E package that could be used by both
XEmacs and GNU Emacs, that would be ideal ;-).
>From the MH-E Makefile:
# Install the source into the Emacs source.
cp $(MH-E-ETC) $(EMACS_HOME)/etc
cp $(MH-E-SRC) $(MH-E-OTHERS) $(EMACS_HOME)/lisp/mh-e
cp $(MH-E-IMG) $(EMACS_HOME)/lisp/toolbar
cp $(MH-E-IMG2) $(EMACS_HOME)/lisp/mail
# View the CVS logs for the Emacs versions (to see if they have been modified).
(cd $(EMACS_HOME)/etc; cvs log $(MH-E-ETC))
(cd $(EMACS_HOME)/lisp/mail; cvs log $(MH-E-SRC) $(MH-E-OTHERS))
(cd $(EMACS_HOME)/lisp/toolbar; cvs log $(MH-E-IMG))
(cd $(EMACS_HOME)/lisp/mail; cvs log $(MH-E-IMG2))
# Import Emacs changes.
Bill Wohler <address@hidden> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
|[Prev in Thread]
||[Next in Thread]|
- Re: Gnus update,
Bill Wohler <=