From: John Keeping <john@keeping.me.uk>
To: git@vger.kernel.org
Cc: John Keeping <john@keeping.me.uk>
Subject: [PATCH 0/2] send-email config path expansion
Date: Tue, 17 Nov 2015 22:01:04 +0000 [thread overview]
Message-ID: <cover.1447797487.git.john@keeping.me.uk> (raw)
These two patches enable tilde-expansion for a few more config variables
in git-send-email.
The first case is the one that surprised me when it didn't work, the
second two are the other ones that look like they should be handled as
paths.
John Keeping (2):
send-email: expand path in sendemail.smtpsslcertpath config
send-email: expand paths in sendemail.{to,cc}cmd config
git-send-email.perl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.6.3.462.gbe2c914
next reply other threads:[~2015-11-17 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 22:01 John Keeping [this message]
2015-11-17 22:01 ` [PATCH 1/2] send-email: expand path in sendemail.smtpsslcertpath config John Keeping
2015-11-17 22:01 ` [PATCH 2/2] send-email: expand paths in sendemail.{to,cc}cmd config John Keeping
2015-11-24 0:04 ` Eric Sunshine
2015-11-24 8:43 ` John Keeping
2015-11-24 22:23 ` Jeff King
2015-11-24 22:58 ` John Keeping
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=cover.1447797487.git.john@keeping.me.uk \
--to=john@keeping.me.uk \
--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).