Re: python.el fixes for Emacs 22

[Barry Warsaw <barry@python.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 21, 2008, at 6:08 PM, Ken Manheimer wrote:

> for allout and other emacs-repository things that i maintain, i have
> my own repositories where i do my development - i can be more casual
> about commitments there - and on suitable occasions i apply the
> changes to the emacs repository version.  i haven't noticed problems
> keeping xemacs compatability for code that lives in the fsf
> repository.  i don't mind the extra step in exchange for the broader
> availability of the code gained by inclusion in emacs, proper, and
> easier access for others wanting to apply fixes.  in general, the
> quality of the developers with emacs repository access is high enough
> that it's a net win.

What vcs is Emacs using these days?  Looks like Arch and/or CVS?

Maybe we should try to do the same thing you're doing with allout, et  
all.  Maintain it separately and sync it to the Emacs repo occasionally?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iQCVAwUBR74FY3EjvBPtnXfVAQI+bgQAroD9RIes/zuTB03526Iu0Sm7hHMTd5qw
LSeySE5u81s/KvnOhVUoEX+Wpg4uu8bnd3nKGZdgCpLXT1x7NtPG0ykNLDgD0ypa
fkTiehTYuMF/DeXTUhgTovTqcuK3T2yDFQ/ie5Vw+mZhZs2us9fIK3bWdtRTMTf9
n3lumwq7eac=
=fg8j
-----END PGP SIGNATURE-----