Linux maintainer tooling and workflows
 help / color / mirror / Atom feed

From: Lucas De Marchi <lucas.demarchi@intel.com>
To: <tools@linux.kernel.org>
Subject: Couple of bugs(?) in b4 send
Date: Thu, 8 Sep 2022 13:13:59 -0700	[thread overview]
Message-ID: <20220908201359.tlm3tlykpsm5j3iu@ldmartin-desk2.lan> (raw)

Trying the new b4 prep/send commands. I used some patches I had and
just created a new series. Some hiccups:

1) --to/--cc don't understand aliases

I use sendemail.aliasesfile in my git config to point to
~/.config/neomutt/aliases. When I try

	b4 send --to intel-gfx --no-sign --no-auto-to-cc --dry-run

the "To:" header is empty instead of looking that up in the aliases
file.

2) --no-auto-to-cc either does too much or too little

I want to Cc people who previously reviewed the patch or who are
explicitely added in Cc in the body of the commit message, i.e. I don't
want --suppress-cc to be given to git-send-email. However I also don't
want the get_maintainer.pl to be invoked since I already reviewed the
list of people I want to send the email to.

If I pass --no-auto-to-cc nobody is included and if I don't,
get_maintainer.pl is called and a lot of people added to the list.

My workaround for both was to use b4 send as a replacement for
git-format-patch only, with the output to a directory, and then use
git-send-email. Patch series is this: https://patchwork.freedesktop.org/series/108315/

thanks
Lucas De Marchi

next             reply	other threads:[~2022-09-08 20:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 20:13 Lucas De Marchi [this message]
2022-09-08 20:39 ` Couple of bugs(?) in b4 send Konstantin Ryabitsev
2022-09-08 22:22   ` Lucas De Marchi
2022-09-09 16:11     ` Konstantin Ryabitsev
2022-09-12 20:47 ` Konstantin Ryabitsev

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=20220908201359.tlm3tlykpsm5j3iu@ldmartin-desk2.lan \
    --to=lucas.demarchi@intel.com \
    --cc=tools@linux.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

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 read-only IMAP folder(s) and NNTP newsgroup(s).