Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: tools@kernel.org
Subject: Re: b4 send support for email alias file
Date: Wed, 7 Aug 2024 09:47:56 -0400	[thread overview]
Message-ID: <20240807-amorphous-vague-markhor-bb1a1d@lemur> (raw)
In-Reply-To: <a6a4755d-85a6-4bc8-83f4-db374c4f3a03@intel.com>

On Tue, Aug 06, 2024 at 02:19:57PM GMT, Jacob Keller wrote:
> I have recently been trying to switch to using b4 as my tool for sending
> patch sets. I previously used git send-email. send-email has support for
> an email alias file which allows specifying shorthand nicknames for
> emails and automatically translating those aliases into the full name
> and email address.

Right, this has come up several times in the past -- the TLDR is that it's not
as straightforward as it seems at first:

https://lore.kernel.org/tools/20231212-illustrious-lion-of-psychology-d85d9d@meerkat/

> Would it be possible to have b4 either handle git's email alias file? Or
> perhaps have its own file/config options?

I have a counter-offer -- suggest on the git list that the --dump-aliases
switch should also have a way to provide destinations, not just aliases
themselves. Then we won't need to support 6 different alias file formats and
can just rely on git doing the translation. :)

-K

  reply	other threads:[~2024-08-07 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 21:19 b4 send support for email alias file Jacob Keller
2024-08-07 13:47 ` Konstantin Ryabitsev [this message]
2024-08-07 21:02   ` Jacob Keller

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=20240807-amorphous-vague-markhor-bb1a1d@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=jacob.e.keller@intel.com \
    --cc=tools@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