From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Tim Orling <tim.orling@konsulko.com>
Cc: alexandre.belloni@bootlin.com, Joshua Watt <jpewhacker@gmail.com>,
docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] contributor-guide: recommend format.forceInBodyFrom
Date: Thu, 2 May 2024 22:53:54 +0200 [thread overview]
Message-ID: <CANNYZj8e5GUq+BuOjKcdontqx4+_sHZbhtz8AubwoNsHOgkB6g@mail.gmail.com> (raw)
In-Reply-To: <CAOyo-84Y6B9kzzwq6MV9zUs55POsmXzt4uwNOk+YQ14+p1rxCg@mail.gmail.com>
On Thu, 2 May 2024 at 22:23, Tim Orling <tim.orling@konsulko.com> wrote:
> The reason for this thread was a comment from RP during the YP Bug Triage meeting that things were different recently, so we are trying to make sure we get this correct.
> Either something changed in groups.io or somewhere else, because my setup only added either of these settings today.
> I have just sent three emails with the same exact patch but different settings to test-list
> (1) both sendemail.from and format.forceInBodyFrom
> (2) only sendemail.from
> (3) neither sendemail.from nor format.forceInBodyFrom
>
> #3 is also the same conditions I used to send the original patch to the oe-core list.
>
> I would have expected to have heard from Alexandre Belloni previously that there was an issue with my setup in #3.
Right so my observations are:
- groups.io sometimes mangles From (with this 'via list' stuff) and
sometimes it doesn't. I can't see a pattern other than it used to
happen less, and lately it seems to happen for everyone including RP
:-/
- git will insert From: into the body when the patch author and
sendemail.from are not the same (as I set up for myself). It will not
do this if they are the same, even when --force-in-body-from is added
or set in a global config. I'm not sure what am I doing wrong, but it
just doesn't work for me :-/ git is at 2.39.2, so maybe this is fixed
in later versions?
Alex
next prev parent reply other threads:[~2024-05-02 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 15:27 [PATCH] contributor-guide: recommend format.forceInBodyFrom Tim Orling
2024-05-02 15:37 ` [docs] " Joshua Watt
2024-05-02 16:12 ` Tim Orling
[not found] ` <17CBB7F2FCD711F1.29540@lists.yoctoproject.org>
2024-05-02 16:23 ` Tim Orling
2024-05-02 19:18 ` Alexandre Belloni
2024-05-02 19:25 ` [docs] " Joshua Watt
2024-05-02 19:45 ` Alexandre Belloni
2024-05-02 20:15 ` Alexander Kanavin
2024-05-02 20:22 ` Tim Orling
2024-05-02 20:53 ` Alexander Kanavin [this message]
[not found] ` <17CBC7546C174761.19168@lists.yoctoproject.org>
2024-05-03 9:23 ` Alexander Kanavin
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=CANNYZj8e5GUq+BuOjKcdontqx4+_sHZbhtz8AubwoNsHOgkB6g@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=jpewhacker@gmail.com \
--cc=tim.orling@konsulko.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).