git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC] send-email aliases when editing patches or using --xx-cmd

From
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr>
Date
Jun 4, 2015, 22:53 UTC
Message-ID
<299923407.139591.1433458411117.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To
<CAPig+cQbOnaNg8dkbFoRrUN47oEAxUNjRXhMK1HSgCLi6ZxHyQ@mail.gmail.com>

On Thu, Jun 4, 2015 at 1:17 PM, Remi LESPINET <remi.lespinet@ensimag.grenoble-inp.fr> wrote:

Show 11 quoted lines
>
> Hi,
>
> Working on git-send-email, I've seen that there's no aliases support
> when manually adding a recipient in a 'To' or 'Cc' field in a patch
> and for the --to-cmd and --cc-cmd.
>
> I would like to add this support, and I wonder if there are reasons
> not to do it.
>
> Thanks.

I just realize that I totally messed up, Of course I don't want to add To or Cc fields to patches.

In fact I want to add aliases support for --to-cmd and --cc-cmd options. But the modification depends on wheter we can use aliases in fields used by send-email (such as author or signoff-by..) when manually editing a patch or not.

Sorry for this mistake :(
Previous: Remi LespinetNext: Allen Hubbe
Message 5 of 7 in “[RFC] send-email aliases when editing patches or using --xx-cmd”
  1. Remi LESPINETJun 4, 2015
  2. Stefan BellerJun 4, 2015
  3. Eric SunshineJun 4, 2015
  4. Remi LespinetJun 4, 2015
  5. Remi LespinetJun 4, 2015
  6. Allen HubbeJun 5, 2015
  7. Allen HubbeJun 5, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.