public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
	i4ldeveloper@listserv.isdn4linux.de, Karsten Keil <kkeil@suse.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: so what *is* obsolete and removable?
Date: Tue, 17 Apr 2007 14:52:48 +0200	[thread overview]
Message-ID: <4624C320.3050206@imap.cc> (raw)
In-Reply-To: <20070416161337.d59f2ea3.randy.dunlap@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

On Mon, 16 Apr 2007 16:13:37 -0700, Randy Dunlap wrote:
> On Tue, 17 Apr 2007 00:39:10 +0200 Tilman Schmidt wrote:
> 
>> We *did* reach a consensus that isdn4linux is not obsolete in the
>> accepted sense of the word, because there is no replacement for it
>> so far.
>> 
>> OTOH I have since submitted (twice, in fact) a patch that would remove
>> the "(obsolete)" label from the Kconfig entry, but somehow nothing
>> ever became of it. My submissions just linger in LKML, uncommented and
>> unmerged.
> 
> Did you submit the patch to Andrew Morton?

No. The recipients I chose were Karsten Keil as the subsystem
maintainer, i4ldeveloper as the subsystem specific list, and LKML.

> Is the patch in the -mm patchset?

No. Should it be? It's not as if there was anything to test.
It's purely a textual change in Kconfig messages.

> Did Karsten ack the patch?

No. He hasn't replied at all.

> If the patch is in -mm and it's not critical (like this subject),
> then it probably won't be merged until after 2.6.21 is released...

Fine by me, as long as it does get merged eventually so I can stop
watching for attempts to remove isdn4linux as obsolete.

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-04-17 13:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 20:55 so what *is* obsolete and removable? Robert P. J. Day
2007-04-15 21:45 ` Jiri Slaby
2007-04-15 21:50 ` Jesper Juhl
2007-04-16 14:44   ` Robert P. J. Day
2007-04-16 14:58     ` Adrian Bunk
2007-04-16 22:39 ` Tilman Schmidt
2007-04-16 23:13   ` Randy Dunlap
2007-04-17 12:52     ` Tilman Schmidt [this message]
2007-04-17 13:40       ` Alan Cox
2007-04-17 15:03         ` Tilman Schmidt
2007-04-17 15:33           ` Alan Cox
2007-04-17 17:55             ` Tilman Schmidt

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=4624C320.3050206@imap.cc \
    --to=tilman@imap.cc \
    --cc=i4ldeveloper@listserv.isdn4linux.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rpjday@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox