All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: "Kristian Høgsberg" <krh@redhat.com>
Subject: Re: [PATCH] Detect key modifier status in 'sleep --interruptible'
Date: Thu, 13 Aug 2009 22:52:05 +0200	[thread overview]
Message-ID: <20090813205205.GM22130@thorin> (raw)
In-Reply-To: <20090812221431.GD11691@riva.ucam.org>

On Wed, Aug 12, 2009 at 11:14:31PM +0100, Colin Watson wrote:
> On Wed, Aug 12, 2009 at 06:10:18PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > Colin Watson wrote:
> > > This is based on previous work in GRUB Legacy by Kristian and Peter
> > > (CCed). Peter tells me that Red Hat has an assignment already on file,
> > > and it looks like mine is finally making some progress ...
> > 
> > We would need RedHat and Kristian to sign some papers.
> 
> Peter said they were already done, but if that's the case then fine.
> Peter/Kristian, can you double-check this?

We don't have any assignment from any Kristian, nor Red Hat, but we do
have one from a Peter.

Which Peter were you talking about?  I don't see him in CC.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-08-13 20:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:35 [PATCH] Detect key modifier status in 'sleep --interruptible' Colin Watson
2009-08-12 16:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 16:15   ` Vladimir 'phcoder' Serbinenko
2009-08-12 22:14   ` Colin Watson
2009-08-13 20:52     ` Robert Millan [this message]
2009-08-13 21:15       ` Colin Watson
2009-08-23 22:46     ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:56       ` Robert Millan
2009-08-23 23:00         ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:03           ` Robert Millan
2009-08-23 23:05             ` Vladimir 'phcoder' Serbinenko
2009-08-25 19:26         ` Robert Millan
2009-08-24  9:24       ` Colin Watson
2009-08-24 12:23         ` Robert Millan
2009-08-24 12:44           ` Robert Millan
2009-08-24 13:27           ` Colin Watson
2009-08-24 14:28             ` Robert Millan
2009-08-24 16:23               ` Colin Watson
2009-08-24 16:56                 ` Colin Watson
2009-08-24 17:03               ` Colin Watson
2009-08-24 22:04           ` Colin Watson
2009-08-24 22:41             ` Robert Millan
2009-08-24 23:02               ` Colin Watson
2009-08-26 15:33                 ` Colin Watson
2009-08-26 18:39                   ` Robert Millan
2009-08-26 20:26                     ` Colin Watson
2009-08-28 12:44                       ` Robert Millan
2009-08-28 13:20                         ` Colin Watson
2009-08-24 12:56         ` Robert Millan
2009-08-13 20:46 ` Robert Millan
2009-08-23 22:27 ` Robert Millan
2009-08-23 22:41   ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:57     ` Robert Millan
2009-08-24  9:11   ` Colin Watson
2009-08-24 11:57     ` Robert Millan
2009-08-24 12:50       ` Vladimir 'phcoder' Serbinenko
2009-08-24 12:58       ` Michal Suchanek
2009-08-24 14:29         ` Robert Millan
2009-08-24 12:59       ` Colin Watson
2009-08-24 13:27       ` Robert Millan

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=20090813205205.GM22130@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    --cc=krh@redhat.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.