From: Pavel Machek <pavel@ucw.cz>
To: David Madore <david.madore@ens.fr>
Cc: Linux Kernel mailing-list <linux-kernel@vger.kernel.org>,
LSM mailing-list <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] new capability patch, version 0.4.2 (now with fs support), part 3/4
Date: Fri, 8 Sep 2006 17:05:52 +0200 [thread overview]
Message-ID: <20060908150552.GG17680@elf.ucw.cz> (raw)
In-Reply-To: <20060908150356.GA12931@clipper.ens.fr>
On Fri 2006-09-08 17:03:56, David Madore wrote:
> 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.
And pointer is what you'll get ;-). Documentation/SubmittingPatches.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-08 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 4:22 [PATCH] new capability patch, version 0.4.2 (now with fs support), part 1/4 David Madore
2006-09-08 4:25 ` [PATCH] new capability patch, version 0.4.2 (now with fs support), part 2/4 David Madore
2006-09-08 4:25 ` [PATCH] new capability patch, version 0.4.2 (now with fs support), part 3/4 David Madore
2006-09-08 14:41 ` Pavel Machek
2006-09-08 15:03 ` David Madore
2006-09-08 15:05 ` Pavel Machek [this message]
2006-09-08 4:27 ` [PATCH] new capability patch, version 0.4.2 (now with fs support), part 4/4 David Madore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060908150552.GG17680@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox