From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] deferred patches
Date: Sun, 23 Sep 2007 13:43:18 +0200 [thread overview]
Message-ID: <5d375e920709230443r18f25df6x479189948e46f314@mail.gmail.com> (raw)
In-Reply-To: <ff845e32c986453cea0cf0dae20b6de6@plan9.bell-labs.com>
Thanks for the prompt repply, I guess I have not been looking closely
enough at the latest patches.
uriel
On 9/23/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> Actually most patches processed recently have not been deferred. A
> few long-outstanding ones that we may eventually apply have been
> tagged as `deferred' and moved into the `saved' queue.
>
>
prev parent reply other threads:[~2007-09-23 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 0:04 Uriel
2007-09-23 3:43 ` geoff
2007-09-23 11:43 ` Uriel [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=5d375e920709230443r18f25df6x479189948e46f314@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).