From: Nicolas Pitre <nico@fluxnic.net> To: Brian Swetland <swetland@google.com> Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>, Pekka Enberg <penberg@kernel.org>, Daniel Walker <dwalker@codeaurora.org>, linux-arm-msm@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>, Jesse Barnes <jbarnes@virtuousgeek.org>, Dima Zavin <dmitriyz@google.com>, Joe Perches <joe@perches.com>, davidb@codeaurora.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 0/7] Nexus One Support Date: Sat, 22 Jan 2011 14:49:33 -0500 (EST) [thread overview] Message-ID: <alpine.LFD.2.00.1101221432360.8580@xanadu.home> (raw) In-Reply-To: <AANLkTi=47z21zExtfHq2WYdUdXeC1rNhe7vQsqPkFsMi@mail.gmail.com> On Sat, 22 Jan 2011, Brian Swetland wrote: > All we ask is that some reasonable acknowledgement of original > authorship is maintained for non-trivial work. A 5-10 line patch that > deals with mechanical issues of board files or cleans stuff up is no > big deal. 100s of lines that represent some real work is something > else. So... What about http://article.gmane.org/gmane.linux.ports.arm.msm/167 ? Is that good enough for you? If no, then could you please propose an alternative? If that is indeed good enough, then could we please move on? > What would be useful would be a reasonable convention for > acknowledging multiple authors, perhaps something along the lines of: > > Author: Awesome Upstreamer <au@example.com> or Main Author <main@example.com> > Committer: Awesome Upstreamer <au@example.com> > Subject: arm: msm8k: acpu clock management > > ... summary of the patch ... > > Original-Author: Joe Firmware Guy <joe@oem.com> > Original-Author: Kernel Droid <droid@android.com> > Signed-off-by: ... > > Though I'm not sure "Original-Author" is the best phrasing here... Or > perhaps just having the patch description end with "This patch is > based on original code by Joe Firmware Guy, Kernel Droid, etc is the > way to go. I do think that for work where there is one clear original > author, it's nice to leave them as the Author, but at the end of the > day, provided the code's heading in the right direction and the > contributors are acknowledged, that's a detail. I think a free form list of contributors in the commit log should be fine, possibly adding them in CC to the patch submission as well. There is a _huge_ value in the action of making code palatable for mainline inclusion and actually pushing that code into mainline. If you do it yourself next time instead of letting your code rot then no one might be tempted to stump on your authorship. Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: nico@fluxnic.net (Nicolas Pitre) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/7] Nexus One Support Date: Sat, 22 Jan 2011 14:49:33 -0500 (EST) [thread overview] Message-ID: <alpine.LFD.2.00.1101221432360.8580@xanadu.home> (raw) In-Reply-To: <AANLkTi=47z21zExtfHq2WYdUdXeC1rNhe7vQsqPkFsMi@mail.gmail.com> On Sat, 22 Jan 2011, Brian Swetland wrote: > All we ask is that some reasonable acknowledgement of original > authorship is maintained for non-trivial work. A 5-10 line patch that > deals with mechanical issues of board files or cleans stuff up is no > big deal. 100s of lines that represent some real work is something > else. So... What about http://article.gmane.org/gmane.linux.ports.arm.msm/167 ? Is that good enough for you? If no, then could you please propose an alternative? If that is indeed good enough, then could we please move on? > What would be useful would be a reasonable convention for > acknowledging multiple authors, perhaps something along the lines of: > > Author: Awesome Upstreamer <au@example.com> or Main Author <main@example.com> > Committer: Awesome Upstreamer <au@example.com> > Subject: arm: msm8k: acpu clock management > > ... summary of the patch ... > > Original-Author: Joe Firmware Guy <joe@oem.com> > Original-Author: Kernel Droid <droid@android.com> > Signed-off-by: ... > > Though I'm not sure "Original-Author" is the best phrasing here... Or > perhaps just having the patch description end with "This patch is > based on original code by Joe Firmware Guy, Kernel Droid, etc is the > way to go. I do think that for work where there is one clear original > author, it's nice to leave them as the Author, but at the end of the > day, provided the code's heading in the right direction and the > contributors are acknowledged, that's a detail. I think a free form list of contributors in the commit log should be fine, possibly adding them in CC to the patch submission as well. There is a _huge_ value in the action of making code palatable for mainline inclusion and actually pushing that code into mainline. If you do it yourself next time instead of letting your code rot then no one might be tempted to stump on your authorship. Nicolas
next prev parent reply other threads:[~2011-01-22 19:49 UTC|newest] Thread overview: 157+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-20 20:32 [PATCH 0/7] Nexus One Support Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 1/7] msm: qsd8x50: add uart platform data Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 2/7] [ARM] msm: qsd8k memory base is at 0x20000000 Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 3/7] msm: qsd8x50: add acpuclock code Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 4/7] msm: mahimahi: add mahimahi board file Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 5/7] msm: mahimahi: add in mmc support code Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 6/7] msm: mahimahi: add gpio pin muxing code Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-20 20:32 ` [PATCH 7/7] msm: mahimahi: initialize mmc at start up Daniel Walker 2011-01-20 20:32 ` Daniel Walker 2011-01-21 0:42 ` [PATCH 0/7] Nexus One Support Dima Zavin 2011-01-21 0:42 ` Dima Zavin 2011-01-21 0:42 ` Dima Zavin 2011-01-21 0:55 ` Daniel Walker 2011-01-21 0:55 ` Daniel Walker 2011-01-21 1:41 ` Joe Perches 2011-01-21 1:41 ` Joe Perches 2011-01-21 1:58 ` Daniel Walker 2011-01-21 1:58 ` Daniel Walker 2011-01-21 2:13 ` Dima Zavin 2011-01-21 2:13 ` Dima Zavin 2011-01-21 15:47 ` Daniel Walker 2011-01-21 15:47 ` Daniel Walker 2011-01-21 2:25 ` Joe Perches 2011-01-21 2:25 ` Joe Perches 2011-01-21 3:41 ` Theodore Tso 2011-01-21 3:41 ` Theodore Tso 2011-01-21 15:46 ` Daniel Walker 2011-01-21 15:46 ` Daniel Walker 2011-01-21 17:48 ` Jesse Barnes 2011-01-21 17:48 ` Jesse Barnes 2011-01-21 17:56 ` Daniel Walker 2011-01-21 17:56 ` Daniel Walker 2011-01-21 17:59 ` Christoph Hellwig 2011-01-21 17:59 ` Christoph Hellwig 2011-01-21 17:56 ` Jesse Barnes 2011-01-21 17:56 ` Jesse Barnes 2011-01-21 17:56 ` Jesse Barnes 2011-01-21 18:00 ` Daniel Walker 2011-01-21 18:00 ` Daniel Walker 2011-01-21 18:04 ` Jesse Barnes 2011-01-21 18:04 ` Jesse Barnes 2011-01-21 18:18 ` Daniel Walker 2011-01-21 18:18 ` Daniel Walker 2011-01-21 18:27 ` Jesse Barnes 2011-01-21 18:27 ` Jesse Barnes 2011-01-21 18:35 ` Daniel Walker 2011-01-21 18:35 ` Daniel Walker 2011-01-21 20:44 ` Dima Zavin 2011-01-21 20:44 ` Dima Zavin 2011-01-21 20:49 ` Daniel Walker 2011-01-21 20:49 ` Daniel Walker 2011-01-21 20:49 ` Daniel Walker 2011-01-21 21:01 ` Jesse Barnes 2011-01-21 21:01 ` Jesse Barnes 2011-01-21 21:01 ` Jesse Barnes 2011-01-21 21:26 ` Daniel Walker 2011-01-21 21:26 ` Daniel Walker 2011-01-21 21:42 ` Dima Zavin 2011-01-21 21:42 ` Dima Zavin 2011-01-21 21:42 ` Dima Zavin 2011-01-22 13:58 ` David Woodhouse 2011-01-22 13:58 ` David Woodhouse 2011-01-21 21:02 ` Joe Perches 2011-01-21 21:02 ` Joe Perches 2011-01-21 21:02 ` Joe Perches 2011-01-21 21:24 ` Daniel Walker 2011-01-21 21:24 ` Daniel Walker 2011-01-21 21:24 ` Daniel Walker 2011-01-22 11:18 ` Pekka Enberg 2011-01-22 11:18 ` Pekka Enberg 2011-01-22 11:18 ` Pekka Enberg 2011-01-22 12:20 ` Russell King - ARM Linux 2011-01-22 12:20 ` Russell King - ARM Linux 2011-01-22 18:06 ` Dima Zavin 2011-01-22 18:06 ` Dima Zavin 2011-01-22 18:06 ` Dima Zavin 2011-01-22 18:49 ` Russell King - ARM Linux 2011-01-22 18:49 ` Russell King - ARM Linux 2011-01-22 18:49 ` Russell King - ARM Linux 2011-01-22 20:50 ` Christoph Hellwig 2011-01-22 20:50 ` Christoph Hellwig 2011-01-22 19:22 ` Brian Swetland 2011-01-22 19:22 ` Brian Swetland 2011-01-22 19:49 ` Nicolas Pitre [this message] 2011-01-22 19:49 ` Nicolas Pitre 2011-01-22 19:59 ` Brian Swetland 2011-01-22 19:59 ` Brian Swetland 2011-01-22 19:59 ` Brian Swetland 2011-01-22 20:53 ` Christoph Hellwig 2011-01-22 20:53 ` Christoph Hellwig 2011-01-22 21:04 ` Russell King - ARM Linux 2011-01-22 21:04 ` Russell King - ARM Linux 2011-01-22 21:57 ` Alan Cox 2011-01-22 21:57 ` Alan Cox 2011-01-23 2:38 ` David Woodhouse 2011-01-23 2:38 ` David Woodhouse 2011-01-22 20:41 ` Christoph Hellwig 2011-01-22 20:41 ` Christoph Hellwig 2011-01-21 21:05 ` Pekka Enberg 2011-01-21 21:05 ` Pekka Enberg 2011-01-21 21:05 ` Pekka Enberg 2011-01-21 21:17 ` Joe Perches 2011-01-21 21:17 ` Joe Perches 2011-01-21 23:49 ` Ted Ts'o 2011-01-21 23:49 ` Ted Ts'o 2011-01-22 0:03 ` Daniel Walker 2011-01-22 0:03 ` Daniel Walker 2011-01-22 1:58 ` Steven Rostedt 2011-01-22 1:58 ` Steven Rostedt 2011-01-22 2:13 ` Daniel Walker 2011-01-22 2:13 ` Daniel Walker 2011-01-22 2:32 ` Steven Rostedt 2011-01-22 2:32 ` Steven Rostedt 2011-01-22 2:31 ` Ted Ts'o 2011-01-22 2:31 ` Ted Ts'o 2011-01-22 8:19 ` Pekka Enberg 2011-01-22 8:19 ` Pekka Enberg 2011-01-22 10:35 ` Dima Zavin 2011-01-22 10:35 ` Dima Zavin 2011-01-22 10:35 ` Dima Zavin 2011-01-22 10:45 ` Anca Emanuel 2011-01-22 10:45 ` Anca Emanuel 2011-01-22 10:45 ` Anca Emanuel 2011-01-22 11:03 ` Pekka Enberg 2011-01-22 11:03 ` Pekka Enberg 2011-01-22 11:15 ` Pekka Enberg 2011-01-22 11:15 ` Pekka Enberg 2011-01-22 17:28 ` Thomas Gleixner 2011-01-22 17:28 ` Thomas Gleixner 2011-01-22 18:07 ` Denis 'GNUtoo' Carikli 2011-01-22 18:07 ` Denis 'GNUtoo' Carikli 2011-01-22 18:07 ` Denis 'GNUtoo' Carikli 2011-01-22 18:15 ` Dima Zavin 2011-01-22 18:15 ` Dima Zavin 2011-01-22 18:15 ` Dima Zavin 2011-01-22 20:55 ` Christoph Hellwig 2011-01-22 20:55 ` Christoph Hellwig 2011-01-22 21:56 ` Pekka Enberg 2011-01-22 21:56 ` Pekka Enberg 2011-01-22 21:56 ` Pekka Enberg 2011-01-22 21:58 ` Christoph Hellwig 2011-01-22 21:58 ` Christoph Hellwig 2011-01-22 22:13 ` Pekka Enberg 2011-01-22 22:13 ` Pekka Enberg 2011-01-22 22:13 ` Pekka Enberg 2011-02-04 13:36 ` Pavel Machek 2011-02-04 13:36 ` Pavel Machek 2011-02-07 17:36 ` Daniel Walker 2011-02-07 17:36 ` Daniel Walker 2011-02-07 17:36 ` Daniel Walker
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=alpine.LFD.2.00.1101221432360.8580@xanadu.home \ --to=nico@fluxnic.net \ --cc=davidb@codeaurora.org \ --cc=dmitriyz@google.com \ --cc=dwalker@codeaurora.org \ --cc=jbarnes@virtuousgeek.org \ --cc=joe@perches.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=penberg@kernel.org \ --cc=swetland@google.com \ /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: linkBe 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.