From: Junio C Hamano <gitster@pobox.com>
To: Allen Hubbe <allenbh@gmail.com>
Cc: git@vger.kernel.org, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v5 1/1] send-email: Add sendmail email aliases format
Date: Mon, 25 May 2015 09:32:23 -0700 [thread overview]
Message-ID: <xmqqpp5obotk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJ80sas_D-6z4MvuFvvjoX7U_bM6b3brCo4rvYFCUfTmKS=6bA@mail.gmail.com> (Allen Hubbe's message of "Mon, 25 May 2015 08:47:32 -0400")
Allen Hubbe <allenbh@gmail.com> writes:
> Looking closer at this and the other test cases, they are inconsistent
> about using ".mailrc", "~/.mailrc", and "$(pwd)/.mailrc". This would
> add another one, "$HOME/.mailrc".
In t9001, I see two tests on mailrc:
* Create .mailrc in the current directory and point at it from the
configuration file sendemail.aliasfile with $(pwd)/.mailrc
This one is correct in that test wants to make sure an absolute
path is usable as the value; the creation in the current
directory (hence >.mailrc) is a mere implementation detail that
the file it wants to use can be created by pathname relative to
the current directory when "echo" is run.
* Create ~/.mailrc, relying on tilde expansion of the shell when
"echo" is run, and then point at it from the configuration file
as "~/.mailrc".
The former, i.e. "echo ... >~/.mailrc" should instead redirect
into >$HOME/.mailrc in order to support shells that do not
understand tilde expansion. However, the latter is correct, as
this test wants to make sure that whoever reads the configuration
interprets ~/.mailrc as "file .mailrc in the home directory",
without help from the shell.
Specifically, the difference between these two tests is not
inconcistency; they are covering two different use patterns.
So I do not see any reason to change most of these; except that the
target of 'echo' should be changed from ~/.mailrc to $HOME/.mailrc.
Thanks.
next prev parent reply other threads:[~2015-05-25 16:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 13:21 [PATCH v5 1/1] send-email: Add sendmail email aliases format Allen Hubbe
2015-05-23 17:45 ` Junio C Hamano
2015-05-23 18:00 ` Junio C Hamano
2015-05-23 23:01 ` Allen Hubbe
2015-05-23 18:07 ` Junio C Hamano
2015-05-23 22:24 ` Allen Hubbe
2015-05-25 12:47 ` Allen Hubbe
2015-05-25 16:32 ` Junio C Hamano [this message]
2015-05-25 21:12 ` Junio C Hamano
2015-05-25 21:35 ` Junio C Hamano
2015-05-26 1:51 ` Allen Hubbe
2015-05-26 1:58 ` Junio C Hamano
2015-05-26 2:16 ` Allen Hubbe
2015-05-26 2:55 ` Junio C Hamano
2015-05-26 3:34 ` Junio C Hamano
2015-05-26 18:47 ` Eric Sunshine
2015-05-26 19:10 ` Eric Sunshine
2015-05-26 19:41 ` Allen Hubbe
2015-05-26 20:53 ` Eric Sunshine
2015-05-26 21:04 ` Allen Hubbe
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=xmqqpp5obotk.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=allenbh@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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.
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).