All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Scott James Remnant <scott@ubuntu.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, dm-devel@redhat.com
Subject: Re: [Kernel PATCH] emit change on devmapper devices
Date: Wed, 7 Nov 2007 11:18:09 -0600	[thread overview]
Message-ID: <20071107171809.GA4239@austin.ibm.com> (raw)
In-Reply-To: <1194454207.6273.5.camel@wing-commander>

On Wed, Nov 07, 2007 at 11:50:07AM -0500, Scott James Remnant wrote:
> Hi guys,
> 
> I've had this patch sitting on my disk for a few months, and haven't
....

On my email reader, I see the following:


[-- PGP output follows (current time: Wed 07 Nov 2007 11:16:06 AM CST) --]
gpg: Signature made Wed 07 Nov 2007 10:50:07 AM CST using DSA key ID C978C8AE
gpg: BAD signature from "Scott James Remnant <scott@ubuntu.com>"
[-- End of PGP output --]

I've never seen a bad signature before ... I thought that was weird.

--linas


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

WARNING: multiple messages have this Message-ID (diff)
From: linas@austin.ibm.com (Linas Vepstas)
To: Scott James Remnant <scott@ubuntu.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, dm-devel@redhat.com
Subject: Re: [Kernel PATCH] emit change on devmapper devices
Date: Wed, 07 Nov 2007 17:18:09 +0000	[thread overview]
Message-ID: <20071107171809.GA4239@austin.ibm.com> (raw)
In-Reply-To: <1194454207.6273.5.camel@wing-commander>

On Wed, Nov 07, 2007 at 11:50:07AM -0500, Scott James Remnant wrote:
> Hi guys,
> 
> I've had this patch sitting on my disk for a few months, and haven't
....

On my email reader, I see the following:


[-- PGP output follows (current time: Wed 07 Nov 2007 11:16:06 AM CST) --]
gpg: Signature made Wed 07 Nov 2007 10:50:07 AM CST using DSA key ID C978C8AE
gpg: BAD signature from "Scott James Remnant <scott@ubuntu.com>"
[-- End of PGP output --]

I've never seen a bad signature before ... I thought that was weird.

--linas


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2007-11-07 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 16:50 [Kernel PATCH] emit change on devmapper devices Scott James Remnant
2007-11-07 16:50 ` Scott James Remnant
2007-11-07 17:18 ` Linas Vepstas [this message]
2007-11-07 17:18   ` Linas Vepstas
2007-11-12 21:20 ` Phillip Susi
2007-11-12 21:20   ` [dm-devel] " Phillip Susi
2007-11-12 21:34   ` Alasdair G Kergon
2007-11-12 21:34     ` [dm-devel] " Alasdair G Kergon

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=20071107171809.GA4239@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=scott@ubuntu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.