From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Michal Marek <mmarek@suse.cz>, Alexey Dobriyan <adobriyan@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ak@linux.intel.com, akpm@linux-foundation.org,
jonas.aberg@stericsson.com, julia@diku.dk,
xiyou.wangcong@gmail.com, yann.morin.1998@anciens.enib.fr,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild misc updates for 2.6.38-rc1
Date: Sat, 8 Jan 2011 17:24:05 +0100 [thread overview]
Message-ID: <20110108162405.GD8237@pengutronix.de> (raw)
In-Reply-To: <4D27A329.7010801@suse.cz>
Hi Michal, hi Alexey,
On Sat, Jan 08, 2011 at 12:35:05AM +0100, Michal Marek wrote:
> On 8.1.2011 00:27, Uwe Kleine-König wrote:
> > Hi Michal,
> >
> > On Sat, Jan 08, 2011 at 12:04:26AM +0100, Michal Marek wrote:
> >> Uwe Kleine-König (1):
> >> tags: put function prototypes back!
> > this is wrong. It was Alexey who authored that patch. I only pinged
> > and forwarded it a few times.
>
> Grr. You should added a second From: header to the message body in that
> case, git am supports this. Rewinding the branch while Linus is possibly
> reviewing it might not be a great idea. Alexey, how much would it hurt
> you if the commit stayed as is?
hmm, actually I know that, and wonder why send-email didn't add it.
... some research ... strange, in my repo I'm already the author for
this patch. So it seems the error is really on my side. I don't
remember but I guess git-am failed for me and then I commited without
taking care to keep the original author. @Alexey: sorry for messing
this up.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-01-08 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 23:04 [GIT] kbuild misc updates for 2.6.38-rc1 Michal Marek
2011-01-07 23:27 ` Uwe Kleine-König
2011-01-07 23:35 ` Michal Marek
2011-01-08 16:24 ` Uwe Kleine-König [this message]
2011-01-08 16:29 ` Alexey Dobriyan
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=20110108162405.GD8237@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jonas.aberg@stericsson.com \
--cc=julia@diku.dk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yann.morin.1998@anciens.enib.fr \
/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