linux-kernel - Re: [GIT] Security subsystem changes for 2.6.38

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: <AANLkTinU2mNyTEc55=ypDPXWah_ozaV1BHWBqCenxp1Z@mail.gmail.com>
Date:	Mon, 10 Jan 2011 11:25:54 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	James Morris <jmorris@...ei.org>
Cc:	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT] Security subsystem changes for 2.6.38

On Sun, Jan 9, 2011 at 4:46 PM, James Morris <jmorris@...ei.org> wrote:
>
> Also, following discussion at the kernel summit, several sub-maintainers
> have now established public git trees from which I pull.

Pulled. However, looking at it, there's a couple of things that
strikes me as having room for improvement. Eg a missing sign-off in
commit 676dac4b1bee, and several "merge branch 'master'" where the
merge message leaves people with absolutely zero idea what the merge
was (which master? What?) or why.

The ability to create merges without any commentary is admittedly a
git misfeature - it's _way_ too easy to create a merge which doesn't
actually tell what's going on. So I apologize for that, but I would
ask people to keep it in mind when doing "git pull" or "git merge" -
think about what the merge message actually tells others about what is
going on.

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