From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Emily Shaffer" <emilyshaffer@google.com>,
git@vger.kernel.org, jrnieder@gmail.com,
jonathantanmy@google.com, steadmon@google.com,
chooglen@google.com, calvinwan@google.com,
workflows@vger.kernel.org
Subject: Re: Why GitGitGadget does not use Sender:, was Re: Review process improvements
Date: Mon, 10 Jan 2022 09:13:27 -0800 [thread overview]
Message-ID: <xmqqwnj71pl4.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2201101401530.339@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 10 Jan 2022 14:03:01 +0100 (CET)")
Konstantin gave a more generally applicable answer to think about
this issue in <20211222213247.5dnj3zlj53lh6l32@meerkat.local> in a
separate thread last year. I would not be surprised if GMail pays
attention to the reasoning he gave in that message and that is the
reason why it does not use the "Sender" as I hoped. I expect other
e-mail providers should do the same.
Thanks.
next prev parent reply other threads:[~2022-01-10 17:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 22:46 Review process improvements Emily Shaffer
2021-12-16 23:22 ` rsbecker
2021-12-17 0:05 ` Junio C Hamano
2021-12-17 18:39 ` Konstantin Ryabitsev
2021-12-20 10:48 ` Christian Couder
2021-12-20 12:29 ` Mark Brown
2021-12-22 3:26 ` Ævar Arnfjörð Bjarmason
2021-12-22 13:07 ` Fabian Stelzer
2021-12-22 15:45 ` Konstantin Ryabitsev
2021-12-22 19:42 ` Junio C Hamano
2021-12-22 21:32 ` Konstantin Ryabitsev
2022-01-10 13:03 ` Why GitGitGadget does not use Sender:, was " Johannes Schindelin
2022-01-10 17:13 ` Junio C Hamano [this message]
2021-12-23 13:50 ` Stefan Hajnoczi
2021-12-20 11:22 ` Ævar Arnfjörð Bjarmason
2021-12-20 17:14 ` Eric Sunshine
2021-12-20 21:27 ` João Victor Bonfim
2022-01-05 1:02 ` Emily Shaffer
2022-01-09 3:26 ` João Victor Bonfim
2021-12-21 1:47 ` brian m. carlson
2022-01-05 0:45 ` Emily Shaffer
2022-01-09 8:26 ` Matthias Aßhauer
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=xmqqwnj71pl4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=calvinwan@google.com \
--cc=chooglen@google.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=steadmon@google.com \
--cc=workflows@vger.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;
as well as URLs for NNTP newsgroup(s).