linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: linuxppc-dev@ozlabs.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Guennadi Liakhovetski <lg@denx.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] LED updates for 2.6.29
Date: Sun, 11 Jan 2009 13:39:05 +0000	[thread overview]
Message-ID: <1231681145.5304.31.camel@dax.rpnet.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0901110416510.1626@shell2.speakeasy.net>

On Sun, 2009-01-11 at 04:58 -0800, Trent Piepho wrote:
> It doesn't seem right to merge someone's patches together, make a very
> small change, and then no longer credit them as the author.  Seems like it
> defeats the purpose of the SOB lines for tracing the train of custody too.
> If someone looks to see where the code came from, it will look like you
> wrote it.  Maybe Freescale will say Intel stole our code?  Without the SOB,
> what record is there in git that Freescale gave permission to put the code
> in the kernel?
> 
> I also put some significant effort into writing informative commit
> messages, which have been lost.  Along with Grant's acks for my patches.

It also doesn't make sense to make three changes adding different
interfaces and rearranging the same section of code three different
times. I'm dropping the patch, please send me a merged version of those
patches with a commit message you're happy with. If you want Acked-by
lines, we'll have to wait for them on the new patch as I'm going to do
this exactly by the book regardless of time pressures now. Please
indicate who you want Ack-ed by lines from so I know who to wait for.
Also, you'd better exclude the suspend/resume change and credit me for
the bitfield change, just to be 100% sure this is all legally accurate.

Regards,

Richard

      reply	other threads:[~2009-01-11 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1231500186.5317.9.camel@dax.rpnet.com>
     [not found] ` <Pine.LNX.4.64.0901091231310.22972@t2.domain.actdsltmp>
     [not found]   ` <1231543199.5317.63.camel@dax.rpnet.com>
2009-01-10 12:31     ` [GIT PULL] LED updates for 2.6.29 Trent Piepho
2009-01-11  0:33       ` Richard Purdie
2009-01-11  1:20         ` Guennadi Liakhovetski
2009-01-11  5:43         ` Trent Piepho
2009-01-11 11:49           ` Richard Purdie
2009-01-11 12:58             ` Trent Piepho
2009-01-11 13:39               ` Richard Purdie [this message]

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=1231681145.5304.31.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=akpm@linux-foundation.org \
    --cc=lg@denx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xyzzy@speakeasy.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.
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 NNTP newsgroup(s).