mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dave Huseby <>
To: Junio C Hamano <>
Cc: "Ævar Arnfjörð Bjarmason" <>,,,,,,,
Subject: Re: [PATCH v3] doc: writing down Git mailing list etiquette
Date: Thu, 13 May 2021 10:17:06 -0700	[thread overview]
Message-ID: <20210513171706.GD11882@localhost> (raw)
In-Reply-To: <xmqqy2cjcwn4.fsf@gitster.g>

On 13.05.2021 09:20, Junio C Hamano wrote:
>I've read this version over, and did not find much that is
>objectionable, but as some others said on the previous round, there
>may be overlaps and repetitions we'd rather get rid of.  We should
>be able to cover discussions around patches in the SubmittingPatches
>document without introducing a new document, so all that remains is
>what to do with non-patch discussions.  I suspect that it might even
>be sufficient to (1) taylor descriptions introduced in this patch
>for discussions around patches and reviews, and add it as a new
>section to SubmittingPatches and (2) mention that the same principle
>applies to non-patch communication in the same section as a sidenote
>but obviously others may disagree.

I realized last night that there is an important distinction between
using email to work *with* Git and using email to work *on* Git. The Git
ML has its own etiquette and rules and MUA tweaks that may not apply to
other projects that use Git and a mailing list. The files
MyFirstContribution.txt and SubmittingPatches are clearly focused on
using email to work *on* Git. The file MyFirstObjectWalk.txt is also
about working *on* Git, although unrelated to email and the mailing
list. Maybe it's time we make the *on*/*with* distinction more obvious
by creating a Documentation/WorkingOnGit subdir? Just throwing that out

It sounds to me like adding a MailingListEtiquette.txt file isn't the
favored approach. I can tailor the information in here to fit into new
sections of SubmittingPatches.

>Ævar, you also have some updates to SubmittingPatches in flight.
>Can I ask you to work with Dave to figure out how well this update
>fits in the entire picture as a stakeholder to the document (i.e.
>not as "the guilty party who is involved in conflicts", but as
>"somebody who has been long enough to be qualified to guide the
>evolution of the document, and obviously is interested in improving
>the document")?

I saw Ævar's patches last night and had the same thought. Since it looks
like this is probably all going into SubmittingPatches, I'll connect
with Ævar and see if we can come up with a patch series for (1) Ævar's
re-org and pruning (2) my Mutt MUA settings and (3) etiquette related
information for discussions around patches and reviews with a (4) side
note for any general etiquette for non-patch communication.



No, thank you. And thank you to Felipe and Bagas for such thorough

  reply	other threads:[~2021-05-13 17:17 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
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 [this message]
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

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210513171706.GD11882@localhost \ \ \ \ \ \ \ \ \ \ \

* 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 public inbox

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).