Sorry if you've done something already, most of this i relevant anyway
I think. But I'm just going straight through my mail, and this is the
end of the thread....
>>>> "Peter" == Peter Brown
<rendhalver(a)users.sourceforge.net> writes:
Peter> Adrian Aichner writes:
> >>>>> "Peter" == Peter Brown
<rendhalver(a)users.sourceforge.net>
> writes:
>
Peter> [snip]
> I'd say, send them to the list.
All patches that are believed to be correct, and are submitted with
the intent to have applied (as opposed to "proof-of-concept" or for
testing for a specific weird, poorly understood problem) should go to
xemacs-patches.
> Create a .tar.gz file if the patch is bigger than 200Kbyte or
> some such number.
Better yet, try to tease apart the various patches. In particular, if
you and Kiriyama-san are in agreement, then I would (as 21.4 Release
Manager) tend to accept all patches which are in freebsd-specific code
(that is, they are guarded by conditionals that reduce to #ifdef
FREEBSD && (...)). OTOH, if the code could get built into a
non-FreeBSD build, I would have to look closely at it personally.
If you and/or kiriyama-san want to maintain these changes in the
XEmacs repository, it might be the best of all possible worlds. You
would get commit authority to 21.5 (but only after approval by a
Review Board member); I and Vin would still have sole authority in our
branches (21.4 and 21.1 respectively). Let me know if you want to do
that (Martin used to handle it). I don't know how we go about adding
comitters at the moment; I'll get back to you on that.
Peter> oki cool ill do it soon
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."