All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marek Lindner <lindner_marek@yahoo.de>
Cc: b.a.t.m.a.n@lists.open-mesh.net, Luis de Bethencourt <luisbg@ubuntu.com>
Subject: Re: [B.A.T.M.A.N.] batman patch authorship mangled
Date: Fri, 7 May 2010 08:26:06 -0700	[thread overview]
Message-ID: <20100507152606.GA18943@kroah.com> (raw)
In-Reply-To: <201005072243.12054.lindner_marek@yahoo.de>

On Fri, May 07, 2010 at 10:43:11PM +0800, Marek Lindner wrote:
> 
> Hi Greg,
> 
> the last patchset sent by Andrew contained a few errors regarding the 
> authorship due to incorrect handling on our side. We did not notice these 
> issues until the patches went out to get included by you.

Ick.

> Here is the complete list of incorrect assignments:
>  * should be Linus instead of Simon
>  => [PATCH 07/26] staging:batman-adv: Remove dead max addr and obsolete 
> VIS_FORMAT strings
>  => [PATCH 09/26] staging:batman-adv: Update README about vis raw output
> 
>  * should be Luis instead of Marek
>  => [PATCH 12/26] staging:batman-adv: fix whitespace style issues
> 
>  * should be Sven instead of Marek
>  => [PATCH 24/26] staging:batman-adv: Fix whitespace problems criticized by 
> checkpatch.pl
>  => [PATCH 25/26] staging:batman-adv: Reduce max characters on a line to 80
> 
> Is there any way to correct the authors of the patches in question ? I know 
> that modifying the git history to fix the author will change all following 
> hashes and everyone has to rebase its tree.
> Personally, I'm not so worried about Linus & Sven, since they are longterm 
> contributors and somewhat close to the project. I'm sure a beer or two can 
> compensate them for the loss of fame. Luis on the other hand seemed to be 
> quite thrilled about getting his patch in and I'd rather not leave him with 
> the impression we don't want to credit him for his work.

Hm, ok, I'll try to rebase the whole tree :(

Can you resend me the set of 26 patches with the correct authorship set
so I know I get it right?

thanks,

greg k-h

  reply	other threads:[~2010-05-07 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 14:43 [B.A.T.M.A.N.] batman patch authorship mangled Marek Lindner
2010-05-07 15:26 ` Greg KH [this message]
2010-05-07 16:42   ` Marek Lindner
2010-05-07 17:41   ` Luis de Bethencourt
2010-05-07 17:56     ` Andrew Lunn
2010-05-07 18:54       ` Luis de Bethencourt
2010-05-11 20:47         ` Greg KH
2010-05-11 22:28           ` Sven Eckelmann
2010-05-11 22:46             ` Luis de Bethencourt

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=20100507152606.GA18943@kroah.com \
    --to=greg@kroah.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=lindner_marek@yahoo.de \
    --cc=luisbg@ubuntu.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 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.