From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] libamcodec: new Package
Date: Tue, 28 Jun 2016 13:24:16 +0200 [thread overview]
Message-ID: <877fd9o8tb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <trinity-d4bed891-c195-45ad-af5c-7e6a2da119ec-1464844313669@3capp-mailcom-bs13> (daggs@gmx.com's message of "Thu, 2 Jun 2016 07:11:53 +0200")
>>>>> "daggs" == daggs <daggs@gmx.com> 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
next prev parent reply other threads:[~2016-06-28 11:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 10:27 [Buildroot] [PATCH 1/3] libamcodec: new Package Dagg
2016-06-01 10:27 ` [Buildroot] [PATCH 2/3] select libamlogic for odroidc2 boards Dagg
2016-06-01 10:27 ` [Buildroot] [PATCH 3/3] allow kodi to select libamlogic if set Dagg
2016-06-04 21:12 ` Bernd Kuhls
2016-06-01 12:16 ` [Buildroot] [PATCH 1/3] libamcodec: new Package Thomas Petazzoni
2016-06-01 20:52 ` daggs
2016-06-01 21:05 ` Thomas Petazzoni
2016-06-01 21:16 ` daggs
2016-06-01 21:28 ` Thomas Petazzoni
2016-06-02 5:11 ` daggs
2016-06-28 11:24 ` Peter Korsgaard [this message]
2016-06-28 11:18 ` Peter Korsgaard
2016-06-04 13:02 ` Thomas Petazzoni
2016-06-04 15:02 ` daggs
2016-06-04 15:53 ` Yann E. MORIN
2016-06-05 5:43 ` daggs
2016-06-01 12:53 ` Vicente Olivert Riera
2016-06-01 13:20 ` Thomas Petazzoni
2016-06-01 13:26 ` Vicente Olivert Riera
2016-06-01 13:33 ` Thomas Petazzoni
2016-06-01 20:58 ` daggs
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=877fd9o8tb.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.