From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] When providing a wildcard as file for an attachment, correctly expand it
Date: Thu, 01 Oct 2009 10:10:12 -0700 [thread overview]
Message-ID: <1254416978-sup-2395@masanjin.net> (raw)
In-Reply-To: <1254343324-sup-7275@midna.zekjur.net>
Reformatted excerpts from Michael Stapelberg's message of 2009-09-30:
> the attached patch will expand wildcards given as filename when adding
> attachments to a message. Thus, you can now add ~/work/foo/* at once.
Branch attach-wildcards, merged into next. Thanks! This is awesome.
> As with the last patch, please review, test and merge.
I changed one minor thing: Dir["#{fn}"] -> Dir[fn]. :)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-10-01 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:43 Michael Stapelberg
2009-10-01 17:10 ` William Morgan [this message]
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=1254416978-sup-2395@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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