git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dave Huseby <dwh@linuxprogrammer.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git@vger.kernel.org, christian.couder@gmail.com,
	felipe.contreras@gmail.com, stefanmoch@mail.de,
	philipoak@iee.email, bagasdotme@gmail.com,
	sunshine@sunshineco.com
Subject: Re: [PATCH v3] doc: writing down Git mailing list etiquette
Date: Fri, 14 May 2021 06:11:34 +0900	[thread overview]
Message-ID: <xmqqk0o29w55.fsf@gitster.g> (raw)
In-Reply-To: <20210513171706.GD11882@localhost> (Dave Huseby's message of "Thu, 13 May 2021 10:17:06 -0700")

Dave Huseby <dwh@linuxprogrammer.org> writes:

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

I agree with that "realization", and think we shouldn't talk
anything about what other people who happens to use Git for their
projects should do, at least for now, when we do not even have a
completed written guideline for ourselves to follow when using Git
for our projects.

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

Sounds good.  Thanks.

  parent reply	other threads:[~2021-05-13 21:11 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 [this message]
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:
  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=xmqqk0o29w55.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=dwh@linuxprogrammer.org \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --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.
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).