From: Marek Vasut <marek.vasut@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Zhang Rui <rui.zhang@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH 1/6] thermal: split thermal_zone_of_sensor_register{,_param}()
Date: Sun, 16 Dec 2018 21:43:11 +0100 [thread overview]
Message-ID: <74305798-9405-4f82-36a6-1f5cc515eaf6@gmail.com> (raw)
In-Reply-To: <CAMuHMdUnH5-YeGcQdbyJP2KNZFS=zxhSb7PZ1ZhLCqFxiw=TnQ@mail.gmail.com>
On 12/16/2018 09:08 PM, Geert Uytterhoeven wrote:
[...]
>>>>> Git actually does that automatically, assumed your user.email config matches
>>>>> the From: address that is used in your outgoing email delivery path (i.e. the
>>>>> scrubbed one, when using Gmail's SMTP server).
>>>>> If you lie to git in your user.email config, git cannot do the right
>>>>> thing, obviously.
>>>>
>>>> My git user.email obviously matches the From: field , before the
>>>> scrubbing, which I believe is the correct thing to do.
>>>
>>> I disagree, because that is not how the emails are actually going out from the
>>> SMTP server you are using.
>>
>> Can you summarize, clearly, what you believe is the right thing to
>> configure and where ?
>
> According to git-send-email(1), you can either pass your scrubbed email
> address to --from, or configure it in the sendemail.from config option.
> Does that work for you?
So sendemail.from != user.email , the later has the +tag while the
former does not ?
>>>>>> from the same person/email address as the email address in From, so they
>>>>>> are equal.
>>>>>
>>>>> If they differ, they are not equal ;-)
>>>>
>>>> Depends on how you define 'equal' . Here I think foo+bar@example.com
>>>> should be considered equal to foo@example.com .
>>>
>>> That is domain-specific knowledge, which you cannot rely upon.
>
>>>> Aha, so maybe that enhancement needs further enhancement to scrub the
>>>> +tags before the check ?
>>>
>>> Again, that is domain-specific knowledge, which you cannot rely upon.
>>
>> How so, please elaborate .
>
> In general, you cannot assume the "+foo" part can be ignored. Only the sender
> knows.
How so ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-12-16 20:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 1:49 [PATCH 0/6] thermal: Align devm_thermal_zone_{device,of_sensor}_register Marek Vasut
2018-12-12 1:49 ` [PATCH 1/6] thermal: split thermal_zone_of_sensor_register{,_param}() Marek Vasut
2018-12-15 17:23 ` Eduardo Valentin
2018-12-15 18:38 ` Marek Vasut
2018-12-15 18:47 ` Geert Uytterhoeven
2018-12-15 18:49 ` Marek Vasut
2018-12-15 18:54 ` Geert Uytterhoeven
2018-12-15 19:07 ` Marek Vasut
2018-12-15 20:00 ` Geert Uytterhoeven
2018-12-15 20:13 ` Marek Vasut
2018-12-16 8:39 ` Geert Uytterhoeven
2018-12-16 17:25 ` Marek Vasut
2018-12-16 17:42 ` Geert Uytterhoeven
2018-12-16 17:48 ` Marek Vasut
2018-12-16 20:08 ` Geert Uytterhoeven
2018-12-16 20:43 ` Marek Vasut [this message]
2018-12-17 13:26 ` Geert Uytterhoeven
2018-12-17 13:28 ` Marek Vasut
2018-12-17 13:36 ` Geert Uytterhoeven
2018-12-17 13:41 ` Marek Vasut
2018-12-17 14:15 ` Geert Uytterhoeven
2018-12-17 15:52 ` Marek Vasut
2018-12-12 1:49 ` [PATCH 2/6] thermal: split devm_thermal_zone_of_sensor_register{,_param}() Marek Vasut
2018-12-12 1:49 ` [PATCH 3/6] thermal: Register hwmon in thermal_zone_of_sensor_register_param() Marek Vasut
2018-12-12 1:49 ` [PATCH 4/6] thermal: stm32: Convert to devm_thermal_zone_of_sensor_register_params() Marek Vasut
2018-12-12 1:49 ` [PATCH 5/6] thermal: rcar_thermal: " Marek Vasut
2018-12-12 1:49 ` [PATCH 6/6] thermal: rcar_gen3_thermal: Register hwmon sysfs interface Marek Vasut
2018-12-14 5:28 ` kbuild test robot
2018-12-15 2:02 ` [PATCH 0/6] thermal: Align devm_thermal_zone_{device,of_sensor}_register Eduardo Valentin
2018-12-15 2:08 ` Marek Vasut
2018-12-15 17:23 ` Eduardo Valentin
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=74305798-9405-4f82-36a6-1f5cc515eaf6@gmail.com \
--to=marek.vasut@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=rui.zhang@intel.com \
--cc=wsa+renesas@sang-engineering.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 NNTP newsgroup(s).