unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph <cschol2112@googlemail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Update keywords/builtins in python.el to Python v2.7 (patch included)
Date: Wed, 07 Jul 2010 06:21:00 -0600	[thread overview]
Message-ID: <4C34712C.7060606@gmail.com> (raw)
In-Reply-To: <4y8w5n3nki.fsf@fencepost.gnu.org>

On 7/6/2010 10:47 PM, Glenn Morris wrote:

> Christoph wrote:
>
>> By bug list you mean bug-gnu-emacs?
>
> Yep.

OK. I will send patches like this to bug-gnu-emacs then. Do I open a bug 
report for every patch or do I just send it to the list directly?

>> I have attached a revised patch minimizing impact on original code
>> and a changelog entry. Hope this helps clarifying the changes. The
>> callable builtins section is a pain, because of the original formatting.
>
> No need to be a slave to alphabetical order.

dir(__builtin__) in Python spits these out in alphabetical order so I 
think it makes sense to keep that for future updates. Ideally, it would 
be formatted as one keyword per line.

> Applied to emacs-23.

Thanks!

Christoph



  reply	other threads:[~2010-07-07 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 20:30 Update keywords/builtins in python.el to Python v2.7 (patch included) Christoph
2010-07-05 22:50 ` Glenn Morris
2010-07-05 23:14   ` Deniz Dogan
2010-07-06  1:49   ` Christoph
2010-07-06 17:28     ` Chong Yidong
2010-07-07  4:47     ` Glenn Morris
2010-07-07 12:21       ` Christoph [this message]
2010-07-07 13:47         ` Davis Herring

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=4C34712C.7060606@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    /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).