From: Greg KH <gregkh@suse.de>
To: ml@mareichelt.de, linux-kernel@vger.kernel.org
Cc: Willy Tarreau <w@1wt.eu>
Subject: Re: Linux 2.6.25.13
Date: Thu, 31 Jul 2008 23:39:02 -0700 [thread overview]
Message-ID: <20080801063902.GA9281@suse.de> (raw)
In-Reply-To: <20080801050214.GE615@1wt.eu>
On Fri, Aug 01, 2008 at 07:02:14AM +0200, Willy Tarreau wrote:
>
> [ please keep people in CC: ]
>
> On Fri, Aug 01, 2008 at 01:22:35AM +0200, markus reichelt wrote:
> > * Greg KH <gregkh@suse.de> wrote:
> >
> > > I'll also be replying to this message with a copy of the patch
> > > between 2.6.25.12 and 2.6.25.13
> >
> > Given that the official patches are signed, how about signing such
> > mails as well?
With what key?
Do you trust my personal key? If so, why? What trust does it imply to
you that my email message doesn't? Why not trust the signature on the
kernel.org server instead?
Also, it makes actually applying patches in the mail a pain, trust me,
I've tried it in the past.
thanks,
greg k-h
prev parent reply other threads:[~2008-08-01 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 18:07 Linux 2.6.25.13 Greg KH
2008-07-28 18:07 ` Greg KH
2008-07-31 23:22 ` markus reichelt
2008-08-01 5:02 ` Willy Tarreau
2008-08-01 6:39 ` Greg KH [this message]
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=20080801063902.GA9281@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@mareichelt.de \
--cc=w@1wt.eu \
/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