All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tilman Schmidt <tilman@imap.cc>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	"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 17:03:58 +0200	[thread overview]
Message-ID: <4624E1DE.2040300@imap.cc> (raw)
In-Reply-To: <20070417144054.24c104bf@the-village.bc.nu>

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

On Tue, 17 Apr 2007 14:40:54 +0100, Alan Cox wrote:
> If the obsolete tag is to be removed then it needs a formal maintainer,
> all the obsolete interface usage cleaning up and the like otherwise at
> some point in a clean up it is going to end up breaking and migrating to
> && BROKEN as well.

I'm not sure I understand. What do you mean by "obsolete interface
usage"? What sort of cleaning up needs to be done? What sort of
breakage do you anticipate in the event of a clean up?

Thanks
Tilman

-- 
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 15:04 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
2007-04-17 13:40       ` Alan Cox
2007-04-17 15:03         ` Tilman Schmidt [this message]
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=4624E1DE.2040300@imap.cc \
    --to=tilman@imap.cc \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.