linux-kernel - Re: [GIT PULL] sh updates for 3.3-rc1

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: <CA+55aFzTJe_VwDxiBKyB3dNCJfm=HXxib4Y4fGihhoBFvXiOTw@mail.gmail.com>
Date:	Wed, 11 Jan 2012 23:29:02 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] sh updates for 3.3-rc1

On Wed, Jan 11, 2012 at 10:51 PM, Paul Mundt <lethal@...ux-sh.org> wrote:
> Here goes my attempt at a merge request by way of signed tag, hopefully
> I've not botched anything too terribly.

Looks fine. Except your key isn't actually signed by anybody I
recognize, so it's kind of worthless that way.

(And it seems to be just a 1024 bit key, which could be improved too)

But the signing part looks technically fine.

> I noticed some people using 3.3 in their signed tags and others with a
> single for-linus one that seems like it will be overwritten on each
> subsequent merge. I've opted for the latter as presumably verification is
> only of interest at the time of merging, but can switch to the former if
> that's the preferred way going forward.

I don't think it matters. Even naming them "3.3" doesn't really make
it any more unique if there are multiple pulls, so I say "whatever
makes sense as a name". If people want to make it clear that it's the
merge pull for the 3.3 release, that's fine. And if they don't, that's
fine too.

You put the "3.3 merge window" in the signed tag itself, and that's
fine too, although that is actually an excellent place to talk about
some high-level details about what that merge brings in. Because the
tag message gets included as part of the merge message (although I can
also edit it), so if you want to talk about the highlights, that's a
great way to do it.

But if there are no real highlights, that's fine too ;)

                   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/