linux-kernel - Re: [PATCH] new capability patch, version 0.4.2 (now with fs support), part 3/4

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: <20060908150356.GA12931@clipper.ens.fr>
Date:	Fri, 8 Sep 2006 17:03:56 +0200
From:	David Madore <david.madore@....fr>
To:	Pavel Machek <pavel@....cz>
Cc:	Linux Kernel mailing-list <linux-kernel@...r.kernel.org>,
	LSM mailing-list <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH] new capability patch, version 0.4.2 (now with fs support), part 3/4

On Fri, Sep 08, 2006 at 04:41:44PM +0200, Pavel Machek wrote:
> Well, for merge you'll need to sign-off and put explanation to each
> patch. Link is not enough, because it will end in git.

You'll have to excuse me for my ignorance: I have some knowledge of
how git and the kernel work as programs, but none at all of how they
are actually managed by the Powers That Be.  So, what does it mean to
"sign off", where should I append the explanations, which git
repository will/might it end in, and how am I supposed to do things
the right way?  I mean, so far I'm just expecting people to read the
patch and perhaps test it, but certainly not commit it anywhere
"serious"...

Pointers are an acceptable answer, of course.

-- 
     David A. Madore
    (david.madore@....fr,
     http://www.madore.org/~david/ )
-
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/