linux-kernel - Re: [git pull] jfs update

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1159803675.10207.15.camel@kleikamp.austin.ibm.com>
Date:	Mon, 02 Oct 2006 10:41:15 -0500
From:	Dave Kleikamp <shaggy@...tin.ibm.com>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] jfs update

On Mon, 2006-10-02 at 08:31 -0700, Linus Torvalds wrote:
> 
> On Mon, 2 Oct 2006, Dave Kleikamp wrote:
> >
> >     Signed-off-by: Dave Kleikamp <shaggy@...tin.ibm.com>
> >     (cherry picked from f74156539964d7b3d5164fdf8848e6a682f75b97 commit)
> 
> Btw, these cherry-pick messages are useless (and just noise) when sending 
> to me, since nobody will likely ever see the private tree that you 
> cherry-picked from, so the SHA1 won't ever match anything meaningful for 
> anybody but you.
> 
> So please either edit it out by hand ("git cherry-pick -e") or just ask 
> git to not generate it at all (the "-r" flag, for "replay"). I thought git 
> had already been fixed to not do this by default, but maybe I was 
> dreaming.

Okay.  This is the first time I used cherry-pick.  Since they were
generated by default, I left it alone.  I'll eliminate them in the
future.

I'm running git-1.4.2.2, which is pretty darn recent, so it doesn't look
like the default has been fixed.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center

-
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/