Simon Ruderich <simon@xxxxxxxxxxxx> writes: > On Thu, Jun 22, 2017 at 01:55:27PM +0000, Patrick Lehmann wrote: >> The description on https://github.com/git/git doesn't reflect that policy. >> >> a) >> It explains that discussions take place in the mentioned mailing list. >> b) >> It describes how to subscribe. > > However it doesn't say that you have to subscribe to send, only > how to subscribe. For that matter, we also say "everyone is welcome to post", which makes it clear that no subscription is required. But I view these merely being technically correct. And making it absolutely obvious does not cost too much. >> With knowledge of other mailing lists (mostly managed by mailman), >> subscription is required for participation. > > That depends on the mailing list, some require subscription to > prevent spams but not all do. Yes. But not many people realize that the world they know is the only world. We are used to an open list and are shocked when we encouter a closed one; let's not forget that shock. How about doing it like this? README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index f17af66a97..bbaf54bffb 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,10 @@ The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@xxxxxxxxxxxxxxx (read [Documentation/SubmittingPatches][] for instructions on patch submission). + +You can send messages without subscribing to the list, but it is +recommended to read what other people are saying on the list before +you speak. To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@xxxxxxxxxxxxxxx. The mailing list archives are available at <https://public-inbox.org/git/>,
