From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Simon Ruderich" <simon@ruderich.org>,
"Patrick Lehmann" <Patrick.Lehmann@plc2.de>,
"Jessie Hernandez" <git@jessiehernandez.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: your mail
Date: Thu, 22 Jun 2017 22:23:17 -0700 [thread overview]
Message-ID: <xmqqshirffay.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170622232156.vptuoafdtglokujw@sigill.intra.peff.net> (Jeff King's message of "Thu, 22 Jun 2017 19:21:56 -0400")
Jeff King <peff@peff.net> writes:
>> +You don't need to be subscribed to the list to send mail to it, and
>> +others on-list will generally CC you when replying (although some
>> +forget this). It's adviced to subscribe to the list if you want to be
>> +sure you're not missing follow-up discussion, or if your interest in
>> +the project is wider than a one-off bug report, question or patch.
>> +
>> The maintainer frequently sends the "What's cooking" reports that
>> list the current status of various development topics to the mailing
>> list. The discussion following them give a good reference for
>
> You perhaps already read it, but you may want to steal wording or
> suggestions from the mailing list section at:
>
> https://git-scm.com/community
>
> which is covering the same ideas (and vice versa, patches to that page
> are welcome if the README says something better).
OK, so... Ævar's version does not mention:
- text/plain, which is a very good addition.
- note about CC in a way as useful as the "community" page does,
which may want to steal from the latter.
- the archive, but it may not be needed in the context of this
document. "Read the archive to make sure you are not repeating
somebody else said before speaking" is something we silently wish
everybody to follow, but it is something we do not want to say
out loud, especially to new people.
- Windows, but I am not sure if it is necessary or even healthy.
One thing I would rather not to see is the Windows mailing list
becomes the first line triage place for any and all issues that
were experienced by a user who happened to be using Windows, and
majority of the issues turn out to be unspecific to Windows. I'd
suspect that all of us rather would want to see the referral go
the other way around.
Otoh, "community" page does not encourage subscription as a way to
ensure you'll see follow-up discussion, which may be a good thing to
add.
A tangent I just found funny is this paragraph on the "community"
page:
The archive can be found on public-inbox. Click here to
subscribe.
Of course clicking does not take you to a subscription page for
public-inbox, even though the two sentences appear to be related.
Perhaps swap the order of the two, like so, with a bit richer
explanation taken from Ævar's version:
... disable HTML in your outgoing messages.
By subscribing (click here), you can make sure you're not
missing follow-up discussion and also learn from other
development in the community. The list archive can be found
on public-inbox.
next prev parent reply other threads:[~2017-06-23 5:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 9:50 Jessie Hernandez
2017-06-22 12:48 ` your mail Simon Ruderich
2017-06-22 13:35 ` AW: " Patrick Lehmann
2017-06-22 13:47 ` Simon Ruderich
2017-06-22 13:55 ` AW: " Patrick Lehmann
2017-06-22 20:46 ` Simon Ruderich
2017-06-22 21:35 ` Junio C Hamano
2017-06-22 21:58 ` Ævar Arnfjörð Bjarmason
2017-06-22 22:14 ` Junio C Hamano
2017-06-22 23:21 ` Jeff King
2017-06-23 5:23 ` Junio C Hamano [this message]
2017-06-23 16:53 ` Jeff King
2017-06-23 18:44 ` Junio C Hamano
2017-06-23 6:58 ` demerphq
-- strict thread matches above, loose matches on Subject: below --
2020-06-24 0:38 shejan shuza
2020-06-24 1:31 ` your mail brian m. carlson
2019-11-20 3:49 Han-Wen Nienhuys
2019-11-20 5:30 ` your mail Taylor Blau
2019-11-20 8:05 ` Christian Couder
2019-07-11 20:11 Robert Morgan
2019-07-11 20:18 ` your mail Kevin Daudt
2019-07-11 20:25 ` Robert Morgan
2019-01-25 9:47 Furkan DURUL
2019-01-25 11:27 ` your mail Kevin Daudt
2016-04-11 19:04 (unknown), miwilliams
2016-04-11 19:13 ` your mail Jeff King
2013-05-17 18:02 (unknown), ASHISH VERMA
2013-05-21 13:13 ` your mail Magnus Bäck
2012-05-06 14:17 (unknown), Bruce Zu
2012-05-06 17:04 ` your mail Marcus Karlsson
2008-08-13 14:54 (unknown), aneesh.kumar
2008-08-13 15:16 ` your mail Aneesh Kumar K.V
2007-12-05 19:00 [PATCH 0/6] builtin-remote Johannes Schindelin
2007-12-05 19:00 ` (unknown) Johannes Schindelin
2007-12-05 19:01 ` your mail Johannes Schindelin
2007-10-13 4:01 (unknown), Michael Witten
2007-10-13 4:07 ` your mail Jeff King
2006-11-21 22:24 (unknown) Johannes Schindelin
2006-11-22 20:16 ` your mail Davide Libenzi
2006-10-20 14:24 (unknown) andyparkins
2006-10-20 14:42 ` your mail Johannes Schindelin
[not found] <C8DBC54F2A9BAD4FA7F445CC7ADD963B0232474F@sslmexchange1.paymentech.us>
2006-09-26 19:56 ` Linus Torvalds
2006-05-21 23:53 (unknown) J. Bruce Fields
2006-05-21 23:55 ` your mail J. Bruce Fields
2006-05-22 0:16 ` Junio C Hamano
2006-05-22 1:33 ` J. Bruce Fields
2005-10-05 6:10 (unknown), Willem Swart
2005-10-06 10:52 ` your mail Elfyn McBratney
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=xmqqshirffay.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Patrick.Lehmann@plc2.de \
--cc=avarab@gmail.com \
--cc=git@jessiehernandez.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=simon@ruderich.org \
/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).