From: Junio C Hamano <gitster@pobox.com>
To: Allen Hubbe <allenbh@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH v4] send-email: Add simple email aliases format
Date: Fri, 22 May 2015 07:44:20 -0700 [thread overview]
Message-ID: <xmqqlhggfz97.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJ80satbXXBYva9qrgR1oA_f7LAHUeAm21=R-mGsWx+sDoQ9sQ@mail.gmail.com> (Allen Hubbe's message of "Fri, 22 May 2015 08:12:39 -0400")
Allen Hubbe <allenbh@gmail.com> writes:
> It depends what we want to do with this parser: accept existing
> sendmail aliases files in git, or enforce that git alias files are
> usable for sendmail. I really don't expect the second to ever happen.
> The first, maybe, but only if the alias file is edited to remove
> aliases of pipes and maildirs etc. The second may not work if we have
> comments to the right, or aliases of aliases, which sendmail does not
> claim to support.
Let me step back a bit. Earlier you said your aim is not to use an
alias file you already have and use with the MUA/MTA, but to have a
collection of aliases to use with git-send-email only. Is there a
reason to add support for a new format (whether it is compatible to
or subset of postfix/sendmail format, or a totally new one) for that
goal? What makes the existing formats unsuitable?
next prev parent reply other threads:[~2015-05-22 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 3:40 [PATCH v4] send-email: Add simple email aliases format Allen Hubbe
2015-05-22 4:29 ` Eric Sunshine
2015-05-22 12:12 ` Allen Hubbe
2015-05-22 14:44 ` Junio C Hamano [this message]
2015-05-22 15:39 ` Allen Hubbe
2015-05-22 17:17 ` Junio C Hamano
2015-05-22 18:03 ` Allen Hubbe
2015-05-22 16:53 ` Eric Sunshine
2015-05-22 18:01 ` Allen Hubbe
2015-05-22 18:49 ` Eric Sunshine
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=xmqqlhggfz97.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=allenbh@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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