All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Greg Bradner <gregb@rhythm.com>
Cc: autofs@linux.kernel.org
Subject: Re: 4.1.4?
Date: Sat, 18 Dec 2004 11:22:30 +0800 (WST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0412181116130.3330@raven-wl.themaw.net> (raw)
In-Reply-To: <41C318E8.4090605@rhythm.com>

On Fri, 17 Dec 2004, Greg Bradner wrote:

> I'm curious too.
> 
> >Ian, when is 4.1.4 coming out.   ;-) 
> >
> >-Jeff

I'm working kernel patch updates now.

I have a couple of difficult daemon patches to merge.
In particular init script patches.

A couple of patches that have been submitted have not been applied, 
largely because of the large number of changes already added. In 
particular the debug info to standard out. I must point out that this is 
not because of problems with the patch but because of the number of 
changes. I don't want to add additional function until this lot has 
settled.

So when?

I should be able to finish over Xmass and get something out in the first 
or second week of Jan.

Ian

      reply	other threads:[~2004-12-18  3:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16  6:27 Limit on return string from program map Keith Owens
2004-12-17  6:23 ` Ian Kent
2004-12-17 15:19   ` Jeff Moyer
2004-12-17 15:40     ` Thomas Jahns
2004-12-17 16:09       ` Jeff Moyer
2004-12-17 17:28     ` Jeff Moyer
2004-12-18  3:23       ` Ian Kent
     [not found]         ` <16838.59899.527170.54922@segfault.boston.redhat.com>
2004-12-20 15:14           ` raven
2004-12-17 17:35     ` 4.1.4? Greg Bradner
2004-12-18  3:22       ` Ian Kent [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=Pine.LNX.4.58.0412181116130.3330@raven-wl.themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=gregb@rhythm.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.