From: Felipe Contreras <felipe.contreras@gmail.com>
To: Dave Huseby <dwh@linuxprogrammer.org>, git@vger.kernel.org
Cc: christian.couder@gmail.com, felipe.contreras@gmail.com,
gitster@pobox.com, stefanmoch@mail.de, philipoak@iee.email,
bagasdotme@gmail.com, sunshine@sunshineco.com, avarab@gmail.com
Subject: RE: [PATCH v3] doc: writing down Git mailing list etiquette
Date: Wed, 09 Jun 2021 12:36:49 -0500 [thread overview]
Message-ID: <60c0fc311144f_1096b2081f@natae.notmuch> (raw)
In-Reply-To: <20210512233412.10737-1-dwh@linuxprogrammer.org>
Dave Huseby wrote:
> After violating a few unspoken etiquette rules while submitting patches
> to the Git mailing list, it was suggeted 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 Git mailing list
> etiquette and the fixes I made to my email setup.
>
> * Add documentation specifically on Git mailing list etiquette
> * Add alternative actions for patches that receive no response.
> * Add section on submitting a final, merge-ready patch.
> * Add section on Mutt MUA settings.
>
> Reported-by: Christian Couder <christian.couder@gmail.com>
> Reported-by: Filipe Contreras <felipe.contreras@gmail.com>
> Thanks-to: Junio C Hamano <gitster@pobox.com>
> Thanks-to: Philip Oakley <philipoakley@iee.email>
> Thanks-to: Bagas Sanjaya <bagasdotme@gmail.com>
> Thanks-to: Eric Sunshine <sunshine@sunshineco.com>
> Thanks-to: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> Signed-off-by: Dave Huseby <dwh@linuxprogrammer.org>
What happened to this? I see value in having this document, so I would
be glad to pick it up if you've lost interest.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-09 17:38 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
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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60c0fc311144f_1096b2081f@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=christian.couder@gmail.com \
--cc=dwh@linuxprogrammer.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoak@iee.email \
--cc=stefanmoch@mail.de \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).