hello waldi, On Thu, Jul 27, 2006 at 10:01:13PM +0200, Bastian Blank wrote: > > debian/patches of linux-2.6 is currently a flat structure, where it is > not really easy to see, what a patch affects.
very nice, some patches should also again be pushed upstream, we collected already lots of cruft afais, too late for 2.6.18, but for the next window. > To make it maybe a little easier I propose a functional structure like > - bugfix/ > Bugfixes or backports. I'm not really happy with that. > - all/ > - $arch/ > - debian/ > Debian specific patches like the version definition. > - features/ > Complete new things. > - all/ > - $feature/ > If the feature needs too many patches, like vserver and xen. > - $arch/ > - security/ > Only security fixes. > - all/, $arch/ > Maybe this can be dropped. ack, although features should stay focussed on special branches that our users need. > - upstream/ > - all/ > For upstream updates like the stable kernel releases. > - $arch/ > Optional, for arches like m68k and hppa with seperate upstream. i fail to see the difference to the bugfix directory, i would skip the bugfix dir, as patches are per se bugfixes. and add an stable subdir to upstream. > To make the life for stable updates easier, which often needs a large > bunch of updates, it may be possible to add support for wildcards in the > series definitions which can be used like > | + security/23etch1/* > to apply all patches in that directory. good idea. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
