From: Barry Warsaw <barry@python.org>
To: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: skip@pobox.com, rms@gnu.org, cyd@stupidchicken.com,
emacs-devel@gnu.org, monnier@iro.umontreal.ca, sdl.web@gmail.com,
nickrob@snap.net.nz
Subject: Re: python.el fixes for Emacs 22
Date: Thu, 21 Feb 2008 18:12:34 -0500 [thread overview]
Message-ID: <70B89BB8-B008-4C7B-B026-C73CA368FB0D@python.org> (raw)
In-Reply-To: <2cd46e7f0802211508w172a4b33p35ee5ca62ae9557@mail.gmail.com>
-----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-----
next prev parent reply other threads:[~2008-02-21 23:12 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 13:34 python.el fixes for Emacs 22 Richard Stallman
2008-02-11 15:15 ` Stefan Monnier
2008-02-11 21:10 ` Richard Stallman
2008-02-12 3:04 ` Stefan Monnier
2008-02-12 17:44 ` Richard Stallman
2008-02-12 21:40 ` Stefan Monnier
2008-02-13 16:32 ` Richard Stallman
2008-02-13 19:19 ` Stefan Monnier
2008-02-14 0:36 ` Chong Yidong
2008-02-14 0:51 ` Miles Bader
2008-02-14 1:56 ` Leo
2008-02-14 18:11 ` Richard Stallman
2008-02-14 23:42 ` Leo
2008-02-15 0:01 ` Nick Roberts
2008-02-15 0:08 ` Leo
2008-02-15 0:17 ` Miles Bader
2008-02-15 2:10 ` Nick Roberts
2008-02-15 17:57 ` Ken Manheimer
2008-02-16 5:53 ` Richard Stallman
2008-02-16 8:18 ` Leo
2008-02-16 8:35 ` Miles Bader
2008-02-16 14:45 ` Stefan Monnier
2008-02-16 14:51 ` Miles Bader
2008-02-17 3:44 ` Stephen J. Turnbull
2008-02-17 13:22 ` Richard Stallman
2008-02-17 13:26 ` Piet van Oostrum
2008-02-15 12:59 ` Richard Stallman
2008-02-15 13:27 ` David Kastrup
2008-02-15 17:43 ` Ken Manheimer
2008-02-15 21:47 ` Nick Roberts
2008-02-15 22:21 ` Ken Manheimer
2008-02-15 23:57 ` Nick Roberts
2008-02-16 0:22 ` Ken Manheimer
2008-02-16 0:39 ` python.el versus python-mode.el [was Re: python.el fixes for Emacs 22] Glenn Morris
2008-02-17 13:22 ` python.el fixes for Emacs 22 Richard Stallman
2008-02-17 13:22 ` Richard Stallman
2008-02-20 0:30 ` Nick Roberts
2008-02-20 2:24 ` pdbtrack [was Re: python.el fixes for Emacs 22] Glenn Morris
2008-02-20 2:34 ` Nick Roberts
2008-02-20 2:56 ` pdbtrack Glenn Morris
2008-02-21 22:40 ` pdbtrack [was Re: python.el fixes for Emacs 22] Ken Manheimer
2008-02-21 23:35 ` pdbtrack Glenn Morris
2008-02-22 18:00 ` pdbtrack Ken Manheimer
2008-02-22 18:35 ` pdbtrack Stefan Monnier
2008-02-23 23:09 ` pdbtrack Ken Manheimer
2008-02-22 20:08 ` pdbtrack Nick Roberts
2008-02-23 23:16 ` pdbtrack Ken Manheimer
2008-02-24 4:49 ` pdbtrack Nick Roberts
2008-02-24 15:40 ` pdbtrack Stefan Monnier
2008-02-24 17:00 ` pdbtrack Ken Manheimer
2008-02-24 20:44 ` pdbtrack Stefan Monnier
2008-02-21 0:20 ` python.el fixes for Emacs 22 Ken Manheimer
2008-02-21 4:02 ` Stefan Monnier
2008-02-21 5:12 ` Barry Warsaw
2008-02-21 22:28 ` Richard Stallman
2008-02-21 23:00 ` Barry Warsaw
2008-02-21 23:08 ` Ken Manheimer
2008-02-21 23:12 ` Barry Warsaw [this message]
2008-02-22 1:49 ` Stefan Monnier
2008-02-22 13:44 ` Barry Warsaw
2008-02-22 15:13 ` skip
2008-02-22 15:30 ` Barry Warsaw
2008-02-22 22:57 ` Richard Stallman
2008-02-22 22:57 ` Richard Stallman
2008-02-22 3:23 ` Stephen J. Turnbull
2008-02-22 13:45 ` Barry Warsaw
2008-02-22 16:28 ` Stefan Monnier
2008-02-22 17:05 ` Barry Warsaw
2008-02-22 17:13 ` Ken Manheimer
2008-02-22 18:27 ` Stefan Monnier
2008-02-22 19:38 ` Barry Warsaw
2008-02-23 19:28 ` Richard Stallman
2008-02-23 20:16 ` skip
2008-02-22 22:57 ` Richard Stallman
2008-02-22 23:33 ` Barry Warsaw
2008-02-23 19:29 ` Richard Stallman
2008-02-23 0:09 ` skip
2008-02-25 13:53 ` Bernhard Herzog
2008-02-21 5:09 ` Barry Warsaw
2008-02-21 5:22 ` Nick Roberts
2008-02-15 16:51 ` Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70B89BB8-B008-4C7B-B026-C73CA368FB0D@python.org \
--to=barry@python.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ken.manheimer@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
--cc=rms@gnu.org \
--cc=sdl.web@gmail.com \
--cc=skip@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).