From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <mail@cbaines.net>,
64151@debbugs.gnu.org
Subject: [bug#64151] [PATCH] etc: Stop making sendemail behave strangely.
Date: Fri, 30 Jun 2023 23:03:52 -0400 [thread overview]
Message-ID: <87ilb41gfb.fsf@gmail.com> (raw)
In-Reply-To: <ce3bf69ac098a41c7111c3f03f5e504e74052d8d.camel@gmail.com> (Liliana Marie Prikler's message of "Wed, 28 Jun 2023 06:30:15 +0200")
Hi Liliana,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Dienstag, dem 27.06.2023 um 21:14 -0400 schrieb Maxim Cournoyer:
>> Hi Liliana,
>>
>> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>> > Funny that you'd mention that because for me, debbugs notifications
>> > are pretty hit or miss. A lot of them end up filtered by our
>> > benevolent overlords without me having ever read them.
>>
>> Maybe you are mistaken about what X-Debbugs-CC does; it doesn't cause
>> someone to be subscribed to a specific issue; it's only a CC
>> alternative that is a bit nicer in that it will reply with the issue
>> number in the reply path, which is mostly useful for new issues that
>> haven't gotten a Debbugs number yet. So I don't think we should
>> think of it as a "notification" mechanism, simply a smarter CC for
>> Debbugs.
> I am not. Debbugs-CC'd mail simply ends up in the spam folder because
> Google sees that
OK, odd; I haven't noticed that kind of filtering using gmail.
>> >
>> > I'd argue that it is wrong to magically install this configuration
>> > without any user interaction. The current setup also causes quite
>> > a number of false positives, like a package rename also causing
>> > changes in some other scope and hence notifying like five different
>> > teams all at once.
>>
>> I personally prefer the zero-config approach that maximizes the
>> potential of etc/teams.scm and reduces the documentation burden, but
>> of course I'm biased :-). I find the contribution process of Guix
>> already complicated enough to not want to add more to it, and welcome
>> automation.
> There's nothing wrong with automation per se, but you are confusing
> automating your own process knowingly with automating someone else's
> process without their knowledge or permission. I'd also argue that
> your approach doesn't maximize etc/teams.scm, but rather makes it
> exhibit the weirdest behaviours imaginable by applying it blindly.
What is weird? People opt to be in a team to be notified; the default
git configuration when submitting patches causes the submission to
notify them when appropriate. I don't understand how that qualifies as
as the "weirdest behaviour imaginable" ?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-07-01 3:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 11:49 [bug#64151] [PATCH] etc: Stop making sendemail behave strangely Christopher Baines
2023-06-25 21:06 ` Ludovic Courtès
2023-06-26 14:36 ` Maxim Cournoyer
2023-06-27 19:26 ` Liliana Marie Prikler
2023-06-28 1:14 ` Maxim Cournoyer
2023-06-28 4:30 ` Liliana Marie Prikler
2023-07-01 3:03 ` Maxim Cournoyer [this message]
2023-07-01 5:50 ` Liliana Marie Prikler
2023-07-01 16:03 ` Maxim Cournoyer
2023-07-03 9:36 ` Ludovic Courtès
2023-07-06 15:49 ` Maxim Cournoyer
2023-07-08 17:16 ` Liliana Marie Prikler
2023-07-10 4:24 ` Maxim Cournoyer
2023-07-10 21:21 ` Ludovic Courtès
2023-07-11 4:28 ` Liliana Marie Prikler
2023-07-14 13:21 ` Ludovic Courtès
2023-07-14 13:52 ` Liliana Marie Prikler
2023-07-14 14:12 ` Maxim Cournoyer
2023-07-14 13:59 ` Maxim Cournoyer
2023-07-17 13:02 ` Christopher Baines
2023-07-17 16:43 ` Maxim Cournoyer
2023-09-06 4:49 ` bug#64151: " Maxim Cournoyer
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=87ilb41gfb.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=64151@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.