From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes for 2.6.33-rc3
Date: Fri, 8 Jan 2010 14:27:15 -0800 [thread overview]
Message-ID: <20100108222715.GC2879@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1001081502480.19243@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [100108 14:03]:
> Hello Linus, Tony,
>
> On Fri, 8 Jan 2010, Tony Lindgren wrote:
>
> > * Linus Torvalds <torvalds@linux-foundation.org> [100108 10:18]:
> > >
> > > There are other problems with that branch too - the "committer"
> > > information is pure sh*t. It says "paul <paul@twilight.(none)>", so quite
> > > frankly, somebody hasn't even read the very first chapter of just about
> > > every single git documentation that is out there.
> > >
> > > And now that I noticed, I see that the crap-for-brains committer info has
> > > been going on for a long time, and I just hadn't looked closely enough
> > > before. I didn't look closely enough to see if the rebase problem had also
> > > happened before.
>
> Sorry - I seem to be the crap-for-brains committer. Will fix -
Here's a check for unconfigured GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL:
$ git log --pretty=oneline --author=".(none)" --committer=".(none)" v2.6.33-rc1..
If it returns results, something is wrong.
Should we have some check like this in place for all pulls?
Regards,
Tony
next prev parent reply other threads:[~2010-01-08 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 18:09 [GIT PULL] omap fixes for 2.6.33-rc3 Tony Lindgren
2010-01-08 18:19 ` Linus Torvalds
2010-01-08 18:22 ` Tony Lindgren
2010-01-08 22:05 ` Paul Walmsley
2010-01-08 22:27 ` Tony Lindgren [this message]
2010-01-08 22:39 ` Linus Torvalds
2010-01-08 22:50 ` Tony Lindgren
2010-01-09 2:47 ` Stephen Rothwell
2010-01-09 17:28 ` Tony Lindgren
2010-01-08 18:20 ` Tony Lindgren
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=20100108222715.GC2879@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).