All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] the scheduled 'time' option removal
Date: Wed, 2 Jan 2008 01:57:01 +0200	[thread overview]
Message-ID: <20080101235701.GJ27566@does.not.exist> (raw)
In-Reply-To: <Pine.LNX.4.64.0801011852250.14900@fbirervta.pbzchgretzou.qr>

On Tue, Jan 01, 2008 at 06:53:54PM +0100, Jan Engelhardt wrote:
> 
> On Jan 1 2008 15:46, Adrian Bunk wrote:
> >index 20c4c8b..93aac19 100644
> >--- a/Documentation/feature-removal-schedule.txt
> >+++ b/Documentation/feature-removal-schedule.txt
> >@@ -233,10 +233,2 @@ Who:	Jean Delvare <khali@linux-fr.org>
> > ---------------------------
> >-
> >-What:	'time' kernel boot parameter
> >-When:	January 2008
> >-Why:	replaced by 'printk.time=<value>' so that printk timestamps can be
> >-	enabled or disabled as needed
> >-Who:	Randy Dunlap <randy.dunlap@oracle.com>
> >-
> 
> I am sure the people who added themselves in the Who: line would have
> taken care of this soon enough, I mean, it's just 19 hours into the
> first day :-)

If Randy decides he wants to submit his own patch for this that wouldn't 
be a problem for me.  :-)

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-01-01 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 13:46 [2.6 patch] the scheduled 'time' option removal Adrian Bunk
2008-01-01 17:53 ` Jan Engelhardt
2008-01-01 23:57   ` Adrian Bunk [this message]
2008-01-02  2:07 ` Randy Dunlap
2008-01-20 14:02   ` Adrian Bunk
2008-01-20 17:31     ` Randy Dunlap

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=20080101235701.GJ27566@does.not.exist \
    --to=bunk@kernel.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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.