From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: git@vger.kernel.org, Jacob Keller <jacob.keller@gmail.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v2 0/3] send-email: teach git send-email mode to translate aliases
Date: Wed, 14 Aug 2024 09:54:45 -0700 [thread overview]
Message-ID: <xmqq34n711uy.fsf@gitster.g> (raw)
In-Reply-To: <20240813-jk-translate-alias-send-email-v2-0-912db4eb6846@gmail.com> (Jacob Keller's message of "Tue, 13 Aug 2024 17:05:08 -0700")
Jacob Keller <jacob.e.keller@intel.com> writes:
> The b4 program has its own "b4 send" utility for sending a patch series. It
> is similar in many respects to git send-email. Currently, it lacks support
> for processing aliases, which makes switching between git send-email and b4
> send somewhat annoying.
>
> It would be convenient if b4 (or other programs interacting with git) could
> make use of git send-email's alias file support.
>
> Teach git send-email a new --translate-aliases option, which enables a new
> mode for git send-email. When executed with this option, git send-email
> will read standard input and convert each input according to the configured
> alias file. The resulting address will be output to standard out.
>
> I also considered implementing a new "full" format for --dump-aliases which
> would dump the entire alias file along with its configured email addresses.
> I ended up dropping that change as I felt that it would be less usable than
> the translation feature.
>
> Signed-off-by: Jacob Keller <jacob.keller@gmail.com>
> ---
> Changes in v2:
> - Use standard input instead of command line arguments
> - Link to v1: https://lore.kernel.org/r/20240808-jk-translate-alias-send-email-v1-0-10a03b3d6b06@gmail.com
>
> ---
> Jacob Keller (3):
> t90001-send-email.sh: fix quoting for mailrc --dump-aliases test
Nobody noticed the typo in the filename since the previous iteration
was posted?
> t9001-send-email.sh: update alias list used for pine test
> send-email: teach git send-email option to translate aliases
>
> Documentation/git-send-email.txt | 7 +++
> git-send-email.perl | 21 ++++++-
> t/t9001-send-email.sh | 118 +++++++++++++++++++++++++++++++++++++--
> 3 files changed, 139 insertions(+), 7 deletions(-)
> ---
> base-commit: 406f326d271e0bacecdb00425422c5fa3f314930
> change-id: 20240808-jk-translate-alias-send-email-1ce048643e5d
>
> Best regards,
next prev parent reply other threads:[~2024-08-14 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 0:05 [PATCH v2 0/3] send-email: teach git send-email mode to translate aliases Jacob Keller
2024-08-14 0:05 ` [PATCH v2 1/3] t90001-send-email.sh: fix quoting for mailrc --dump-aliases test Jacob Keller
2024-08-14 16:56 ` Junio C Hamano
2024-08-14 0:05 ` [PATCH v2 2/3] t9001-send-email.sh: update alias list used for pine test Jacob Keller
2024-08-14 17:02 ` Junio C Hamano
2024-08-14 17:47 ` Jacob Keller
2024-08-14 0:05 ` [PATCH v2 3/3] send-email: teach git send-email option to translate aliases Jacob Keller
2024-08-14 16:54 ` Junio C Hamano [this message]
2024-08-14 17:45 ` [PATCH v2 0/3] send-email: teach git send-email mode " Jacob Keller
2024-08-14 18:41 ` Junio C Hamano
2024-08-15 14:29 ` Konstantin Ryabitsev
2024-08-15 22:57 ` Junio C Hamano
2024-08-15 23:46 ` Keller, Jacob E
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=xmqq34n711uy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jacob.keller@gmail.com \
--cc=konstantin@linuxfoundation.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).