From: Greg KH <greg@kroah.com>
To: Luis de Bethencourt <luisbg@ubuntu.com>
Cc: b.a.t.m.a.n@lists.open-mesh.net,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Marek Lindner <lindner_marek@yahoo.de>
Subject: Re: [B.A.T.M.A.N.] batman patch authorship mangled
Date: Tue, 11 May 2010 13:47:48 -0700 [thread overview]
Message-ID: <20100511204748.GA12704@kroah.com> (raw)
In-Reply-To: <g2t506b70dc1005071154q6764e0bapdc4f8a3a48b4d3d4@mail.gmail.com>
On Fri, May 07, 2010 at 07:54:36PM +0100, Luis de Bethencourt wrote:
> On Fri, May 7, 2010 at 6:56 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> >> Greg, wait!
> >>
> >> No need for this. I understand the problem, can imagine why it
> >> happened and I don't mind the wrong authorship. I prefer avoiding the
> >> general head-ache of rebasing the whole tree.
> >>
> >> To be honest I noticed this in yesterday's emails but I decided to not
> >> mention it.
> >>
> >> Marek,
> >> Any beers for me then :P
> >
> > So, i will wait until somebody has time to visit the post office and
> > work out which is cheaper: Beer to Greg, or Beer to Luis.
> >
> > Andrew
> >
>
> Make it for Greg :)
Ok, I've rebased the staging-next tree on 2.6.34-rc6, reapplied the
patches, and then took your 26 patches and applied them and pushed
everything out.
Can someone verify that I got it all correct?
Oh, and you owe me one bottle of "Tactical Nuclear Penguin" :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-11 20:47 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
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 [this message]
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=20100511204748.GA12704@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=devel@linuxdriverproject.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.