From: Kevin Hilman <khilman@deeprootsystems.com>
To: Patrick Pannuto <ppannuto@codeaurora.org>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm\@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-omap\@vger.kernel.org" <linux-omap@vger.kernel.org>,
"damm\@opensource.se" <damm@opensource.se>,
"lethal\@linux-sh.org" <lethal@linux-sh.org>,
"rjw\@sisk.pl" <rjw@sisk.pl>,
"eric.y.miao\@gmail.com" <eric.y.miao@gmail.com>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
alan@lxorguk.ukuu.org.uk, zt.tmzt@gmail.com,
grant.likely@secretlab.ca, magnus.damm@gmail.com
Subject: Re: [PATCH] platform: Facilitate the creation of pseduo-platform busses
Date: Thu, 05 Aug 2010 15:24:31 -0700 [thread overview]
Message-ID: <87eiecr940.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4C5AE75F.5020507@codeaurora.org> (Patrick Pannuto's message of "Thu, 05 Aug 2010 09:31:27 -0700")
Patrick Pannuto <ppannuto@codeaurora.org> writes:
>>
>>> You had indicated that you were going on vacation for a month and I
>>> had not seen any more follow-up on this issue, so I forged ahead.
>>
>> Great, I'm glad you forged ahead. There is definitely a broader need
>> for something like this, and I have no personal attachment to the code.
>>
>> I have no problems with you continuing the work (in fact, I'd prefer it.
>> I have lots of other things to catch up on after my vacation.)
>>
>> In the future though, it's common (and kind) to note the original author
>> in the changelog when basing a patch on previous work. Something like
>> "originally written by..." or "based on the work of..." etc.
>
> Ok, I can do that; that was the intention of the "original inspiration from"
> line at the beginning.
Maybe we need an 'Inspired-by:' tag. :)
> Is there a more formal way of indicating this in the
> next version of the patch? Should I add you as a "From:" or an "Author:"?
I don't know if there is an official way of doing this.
I typically add something like "based on the idea/code originally
proposed/written by John Doe" in the changelog, and then add Cc: John
Doe <...> in the changelog too, but AFAIK, none of this is formalized.
Kevin
next prev parent reply other threads:[~2010-08-05 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 22:14 [PATCH] platform: Facilitate the creation of pseduo-platform busses Patrick Pannuto
2010-08-05 0:16 ` Kevin Hilman
2010-08-05 0:57 ` Patrick Pannuto
2010-08-05 15:57 ` Kevin Hilman
2010-08-05 16:31 ` Patrick Pannuto
2010-08-05 22:24 ` Kevin Hilman [this message]
2010-08-05 23:16 ` Grant Likely
2010-08-06 1:25 ` Patrick Pannuto
2010-08-07 6:53 ` Grant Likely
2010-08-05 2:32 ` Magnus Damm
2010-08-05 15:27 ` Kevin Hilman
2010-08-05 17:43 ` Patrick Pannuto
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=87eiecr940.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=damm@opensource.se \
--cc=eric.y.miao@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@suse.de \
--cc=lethal@linux-sh.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ppannuto@codeaurora.org \
--cc=rjw@sisk.pl \
--cc=zt.tmzt@gmail.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox