From: "Ævar Arnfjörð Bjarmason" <email@example.com>
To: Dave Huseby <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org,
Subject: Re: [PATCH v2] Writing down mail list etiquette.
Date: Wed, 12 May 2021 10:45:39 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On Tue, May 11 2021, Dave Huseby wrote:
> After violating a few unspoken etiquette rules that were spotted by
> Christian Couder <firstname.lastname@example.org>, Filipe Contreras
> <email@example.com> suggested that somebody write a guide.
> Since I was the latest cause of this perenial discussion, I took it upon
> myself to learn from my mistakes and document the fixes.
> Thanks to Junio <firstname.lastname@example.org> for providing links to similar
> discussions in the past and Stefan Moch <email@example.com> for
> pointing out where the related documentation already existed in the
Improvements in this area are most needed, so thanks for working on
We should not have a new file describing this though, we already cover
the content you're adding here partially in
Documentation/SubmittingPatches, and some more in
Documentation/MyFirstContribution.txt (e.g. a passing mention of
in-reply-to etiquette), with this applied we'd have discussion of these
related topics in three places.
I had some rough WIP patches to update Documentation/SubmittingPatches
to address some of what you're adding here, which I've discarded, but I
submitted some related patches just now as .
As you can see from that topic we e.g. already have MUA-specific tips in
Documentation/SubmittingPatches, your addition of a section discussing
mutt's config here is another thing we'd be duplicating/unnecessarily
splitting across multiple places.
I do think it's going to be hard to update SubmittingPatches, for
example it has a long section going on about the specific format of
patches to craft for the ML, as if anyone's using anything other than
git-format-patch these days (it was written before that existed/was as
I suspect though that any suggestion to simply remove most/all of that
for simplicity will probably be met with (IMO unwarranted resistance),
which is why I gave up on this the other day before even submitting
patches to the ML.
But regardless of that, the post-image after your patch of having
another place we discuss the same/related topic would be worse, we
really should have one canonical guide, so your patch(es) should be
amending/splitting Documentation/SubmittingPatches, not duplicating it.
next prev parent reply other threads:[~2021-05-12 8:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 2:54 [PATCH v1] Writing down mail list etiquette Dave Huseby
2021-05-12 2:57 ` Dave Huseby
2021-05-12 6:25 ` Felipe Contreras
2021-05-12 3:18 ` Dave Huseby
2021-05-12 3:18 ` [PATCH v2] Writing down mail list etiquette Dave Huseby
2021-05-12 4:07 ` Bagas Sanjaya
2021-05-12 6:45 ` Felipe Contreras
2021-05-12 7:35 ` Eric Sunshine
2021-05-12 8:32 ` Felipe Contreras
2021-05-12 14:36 ` Junio C Hamano
2021-05-12 4:46 ` Junio C Hamano
2021-05-12 8:45 ` Ævar Arnfjörð Bjarmason [this message]
2021-05-12 23:34 ` [PATCH v3] doc: writing down Git mailing " Dave Huseby
2021-05-13 0:20 ` Junio C Hamano
2021-05-13 17:17 ` Dave Huseby
2021-05-13 20:04 ` Felipe Contreras
2021-05-13 21:11 ` Junio C Hamano
2021-05-13 4:06 ` Bagas Sanjaya
2021-05-13 6:34 ` Felipe Contreras
2021-05-13 7:01 ` Bagas Sanjaya
2021-06-09 17:36 ` Felipe Contreras
2021-06-18 20:43 ` Dave Huseby
2021-06-18 23:48 ` Felipe Contreras
2021-05-12 15:28 ` and... Re: [PATCH v1] Writing down mail " Philip Oakley
2021-05-12 6:21 ` Felipe Contreras
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).