From: Karl Wiberg <kha@treskal.com>
To: Alex Chiang <achiang@hp.com>
Cc: catalin.marinas@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH 3/6] stg mail: make __send_message do more
Date: Sun, 29 Nov 2009 22:23:00 +0100 [thread overview]
Message-ID: <b8197bcb0911291323l35cb3624td3cbc393bf4513b3@mail.gmail.com> (raw)
In-Reply-To: <20091128195026.949.1772.stgit@bob.kio>
On Sat, Nov 28, 2009 at 8:50 PM, Alex Chiang <achiang@hp.com> wrote:
> Factor out the common code required to send either a cover mail
> or patch, and implement it in __send_message.
Nice code size reduction.
> + msg_id = email.Utils.make_msgid('stgit')
> + build = { 1: __build_cover, 4: __build_message }
> + msg = build[len(args)](tmpl, msg_id, options, *args)
> +
> + from_addr, to_addrs = __parse_addresses(msg)
> + msg_str = msg.as_string(options.mbox)
> + if options.mbox:
> + out.stdout_raw(msg_str + '\n')
> + return msg_id
> +
> + outstr = { 1: 'the cover message', 4: 'patch "%s"' % args[0] }
> + out.start('Sending ' + outstr[len(args)])
You could consolidate the two dictionaries like this, to avoid making
the same choice twice and make the code more pleasant to read:
(build, outstr) = { 1: (__build_cover, 'the cover message'), 4:
(__build_message, 'patch "%s"' % args[0]) }
> + # give recipients a chance of receiving related patches in correct order
> + # patch_nr < total_nr
> + if len(args) == 1 or (len(args) == 4 and args[1] < args[2]):
> + sleep = options.sleep or config.getint('stgit.smtpdelay')
> + time.sleep(sleep)
Hmm. I must say I find all the args[x] a bit hard to read. I'd prefer
symbolic names.
--
Karl Wiberg, kha@treskal.com
subrabbit.wordpress.com
www.treskal.com/kalle
next prev parent reply other threads:[~2009-11-29 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 19:50 [StGit RFC PATCH 0/6] add support for git send-email Alex Chiang
2009-11-28 19:50 ` [PATCH 1/6] stg mail: Refactor __send_message and friends Alex Chiang
2009-11-29 9:13 ` Karl Wiberg
2009-11-30 23:58 ` Alex Chiang
2009-11-28 19:50 ` [PATCH 2/6] stg mail: reorder __build_[message|cover] parameters Alex Chiang
2009-11-28 19:50 ` [PATCH 3/6] stg mail: make __send_message do more Alex Chiang
2009-11-29 21:23 ` Karl Wiberg [this message]
2009-11-30 23:59 ` Alex Chiang
2009-12-01 7:26 ` Karl Wiberg
2009-11-28 19:50 ` [PATCH 4/6] stg mail: factor out __update_header Alex Chiang
2009-11-28 19:50 ` [PATCH 5/6] stg mail: add basic support for git send-email Alex Chiang
2009-11-29 21:54 ` Karl Wiberg
2009-12-01 0:00 ` Alex Chiang
2009-12-01 7:33 ` Karl Wiberg
2009-11-28 19:50 ` [PATCH 6/6] stg mail: don't parse To/Cc/Bcc in --git mode Alex Chiang
2009-11-29 22:05 ` [StGit RFC PATCH 0/6] add support for git send-email Karl Wiberg
2009-12-01 0:02 ` Alex Chiang
2009-12-01 7:38 ` Karl Wiberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b8197bcb0911291323l35cb3624td3cbc393bf4513b3@mail.gmail.com \
--to=kha@treskal.com \
--cc=achiang@hp.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).