>>>> Jan Vroonhof writes:
Jan> Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes:
> How are patches sent to xemacs-patches handled at the moment?
Jan> Extremely ad-hoc. AFAICS nobody is applying patches to the packages at
Jan> the moment.
> Is anyone applying the patches sent there by people without
cvs-write
> access?
Jan> Andy and Michael have applied most them. Normally Steve applies all
Jan> that were left out, just before a new beta releases.
> We should really make sure we do not lose any patches and that
> everything that is applied to 21.1 is also applied to 21.2!
Jan> Yes. We need some explicit tracker system (that is what xemacs-review
Jan> is meant for but I am not sure it is working properly). There is a
Jan> whole lot of patches to the packages that are "in the queue" for two
Jan> months now. I would love it if there were some system in there
Jan> somewhere. For instance there is a patch from _February_ about esound
Jan> support that I still want look at (I didn't have esound at the time).
Hi,
can I help out? After considering this for some time, I'm
volunteering to help.
I should have enough time to keep the CVS archive for the packages
uptodate.
For those who don't know me, let me introduce myself briefly. I'm one
of the glibc developers and XEmacs is one of my favorite programs. In
mid 1997 I helped to get XEmacs running with glibc2 - and since I'm
always using glibc testreleases, XEmacs still works with glibc;-).
I'm currently employed by the Linux distributor SuSE and have spent
some time during the last weeks to get a mule enabled XEmacs 21.1.7
on our next distribution.
Andreas
--
Andreas Jaeger
SuSE Labs aj(a)suse.de
private aj(a)arthur.rhein-neckar.de