From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <nigel@tuxonice.net>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: My patch set forgotten?
Date: Sat, 31 Jul 2010 16:00:29 +0200 [thread overview]
Message-ID: <201007311600.29679.rjw@sisk.pl> (raw)
In-Reply-To: <4C537A9A.3010602@tuxonice.net>
On Saturday, July 31, 2010, Nigel Cunningham wrote:
> Hi Rafael.
Hi,
> It's been a month or so since I sent my patchset, and I haven't seen any
> feedback / merging / whatever. Would you please let me know what's going
> on?
Sorry for the delay, I'll do my best to send you comments on the patches in the
next few days.
> I'm more than happy to rework them to go on top of Jiri's patches,
> but I'm hanging off making more until you give me feedback on the last lot.
The Jiri's patchset is going to change to take some of my comments into
account.
Rafael
prev parent reply other threads:[~2010-07-31 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 1:21 My patch set forgotten? Nigel Cunningham
2010-07-31 14:00 ` Rafael J. Wysocki [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=201007311600.29679.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jslaby@suse.cz \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@tuxonice.net \
/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