From: Patrick Lehmann <Patrick.Lehmann@plc2.de>
To: Simon Ruderich <simon@ruderich.org>
Cc: Jessie Hernandez <git@jessiehernandez.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: AW: your mail
Date: Thu, 22 Jun 2017 13:55:27 +0000 [thread overview]
Message-ID: <0092CDD27C5F9D418B0F3E9B5D05BE080102A423@SBS2011.opfingen.plc2.de> (raw)
In-Reply-To: <20170622134708.fcc4zxakga6p255x@ruderich.org>
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.
With knowledge of other mailing lists (mostly managed by mailman),
subscription is required for participation.
________________________________________
Von: Simon Ruderich [simon@ruderich.org]
Gesendet: Donnerstag, 22. Juni 2017 15:47
Bis: Patrick Lehmann
Cc: Jessie Hernandez; git@vger.kernel.org
Betreff: Re: your mail
On Thu, Jun 22, 2017 at 01:35:33PM +0000, Patrick Lehmann wrote:
> But how can he write to the mailing list without a subscription?
> Is this a security bug or is he already subscribed?
Everybody can send to this mailing list. This is by design so
contributors/bug reporters can send mails without having to
subscribe.
Regards
Simon
--
+ Privatsphäre ist notwendig
+ Ich verwende GnuPG http://gnupg.org
+ Öffentlicher Schlüssel: 0x92FEFDB7E44C32F9
next prev parent reply other threads:[~2017-06-22 13:55 UTC|newest]
Thread overview: 14+ 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 ` Patrick Lehmann [this message]
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
2017-06-23 16:53 ` Jeff King
2017-06-23 18:44 ` Junio C Hamano
2017-06-23 6:58 ` demerphq
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=0092CDD27C5F9D418B0F3E9B5D05BE080102A423@SBS2011.opfingen.plc2.de \
--to=patrick.lehmann@plc2.de \
--cc=git@jessiehernandez.com \
--cc=git@vger.kernel.org \
--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).