Re: Status of kernel patch packages
- To: Hideki Yamane <email@example.com>
- Cc: Yann Dirson <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: Re: Status of kernel patch packages
- From: Yann Dirson <email@example.com>
- Date: Tue, 23 Mar 2010 23:35:33 +0100
- Message-id: <20100323223533.GA11645@nan92-1-81-57-214-146.fbx.proxad.net>
- In-reply-to: <firstname.lastname@example.org>
- References: <20100320141459.GQ8106@nan92-1-81-57-214-146.fbx.proxad.net> <email@example.com>
On Sun, Mar 21, 2010 at 12:17:22AM +0900, Hideki Yamane wrote:
> On Sat, 20 Mar 2010 15:14:59 +0100
> Yann Dirson <firstname.lastname@example.org> wrote:
> > So the question is, is it time to request removal of those packages,
> > or is there any remaining reason not to do so that I missed ?
> As linux-patch-tomoyo1.7 package maintainer, tomoyo is merged with
> mainline, but it's not fully featured one yet. At least, I want to
> provide it with squeeze.
> and hope kernel-package would enable patch support again... ;)
I won't speak for Manoj here, but I feel we should think about other
ways to provide those patches.
One way could be simply to provide ensure those patches in some git
tree, that users can easily fetch and merge before running make-kpkg.
But I'm not aware of a git tree holding the debian kernels - SVN is
still listed as the VCS for the linux-2.6 package (which, BTW,
continues to surprise me). But at least we could have some convention
about where to make available git trees for patch stacks - something
on git.debian.org surely, which could be quite efficient with the
"forks" feature of gitweb activated (which does not seems to be the
Then maybe some simple helper scripts could make it a snap to fetch
all patch stacks and start a merge. Maybe we could at some point also
be able to publish merges of conflicting patch stacks in a similarly
convenient way. Such a resource may even be interesting to many
people out of Debian.
Well, that's just random week-end thoughts - you know, world
domination and the like :)