From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Tue, 28 Jun 2016 13:24:16 +0200 Subject: [Buildroot] [PATCH 1/3] libamcodec: new Package In-Reply-To: (daggs@gmx.com's message of "Thu, 2 Jun 2016 07:11:53 +0200") References: <20160601102720.3929-1-daggs@gmx.com> <20160601141655.5649aa21@free-electrons.com> <20160601230533.04ca63d0@free-electrons.com> <20160601232826.2aa6d899@free-electrons.com> Message-ID: <877fd9o8tb.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "daggs" == daggs writes: Hi, >> I fully respect this choice. There are however some legal aspects to >> take care of as well, so I guess it should be a decision of the >> Buildroot community to accept or not patches that are submitted under a >> pseudonym or anonymously. > sorry for making this harder. > is there another way to verify with without placing such info? > what prevents me for example from sending patches under your name? > isn't it just a text? It is "just text", just like a signature. What is the problem with using your full name? I see you did so in your >From on the v2 patches any way and there's plenty of google hits on your email address. -- Bye, Peter Korsgaard