linux-kernel - Re: [GIT PULL] Block IO fixes for 3.12

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130922235653.GH31014@kernel.dk>
Date:	Sun, 22 Sep 2013 17:56:53 -0600
From:	Jens Axboe <axboe@...nel.dk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>, Mike Christie <michaelc@...wisc.edu>
Subject: Re: [GIT PULL] Block IO fixes for 3.12

On Sun, Sep 22 2013, Linus Torvalds wrote:
> On Sun, Sep 22, 2013 at 4:12 PM, Jens Axboe <axboe@...nel.dk> wrote:
> >
> > Not necessarily bad quality control, but yeah, the commit messages
> > could've been prettier. Those two should have been git ammended, most of
> > them are directly applied byt git am fwiw.
> 
> No, one of them was clearly *not* done with git am, because git am
> uses the subject like to create that summary message.

So make that a combo of git am and shitty mailer. I forget why it
happens, but it does happen often for me and I (usually remember) to fix
it up.

> And the other one you should have edited the mbox before feeding it to
> git am - or pushed back on the submitter to write email in a format
> where no such editing is necessary.
> 
> "I used git am" is not an excuse for bad formatting of commits. It's
> just a tool, you need to make sure the tool is fed valid data.

Sure, not disagreeing. It is my fault :-)

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/