From: Sascha Hauer <s.hauer@pengutronix•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: not a good commit message in i.MX tree
Date: Fri, 10 Dec 2010 09:57:05 +0100 [thread overview]
Message-ID: <20101210085705.GU6017@pengutronix.de> (raw)
In-Reply-To: <20101210092457.a6942195.sfr@canb.auug.org.au>
Hi Stephen,
On Fri, Dec 10, 2010 at 09:24:57AM +1100, Stephen Rothwell wrote:
> Hi Sascha,
>
> Looking through the updates for linux-next today I noticed commit 3ed005593e9a8aa9183c9e827ca0f68a685f25a9 whose whole commit message is:
>
> blibb
>
> Please write a better one.
Uh, the whole patch shouldn't be there. I accidently merged some
temporary branch. Thanks for noting. I fixed this.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2010-12-10 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:24 linux-next: not a good commit message in i.MX tree Stephen Rothwell
2010-12-10 8:57 ` Sascha Hauer [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=20101210085705.GU6017@pengutronix.de \
--to=s.hauer@pengutronix$(echo .)de \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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