Re: adding m68k to svn
On Wed, 20 Oct 2004 21:02:53 +0200, Christian T. Steigies wrote:
> Hi,
> I just added kernel-patch and -image 2.6.8 for m68k to svn. Guess I don't
> have to ask anymore if I can submit binary files, ie gzipped patches, it
> seems to have worked. I haven't seen gzipped files in the other arches, so
> maybe for 2.6.9 I should change that?
If you keep kernel-patch-2.6.8-m68k, I suppose you can do whatever you
want w/ your patches. I don't see the need to gzip them, though; when
packaged, everything gets gzipped anyways in the source packages. I'm not
even sure what dpkg-buildpackage will do w/ binary file changes (ie,
updated gzip patches).
>
> Wrt to patches, to get them included in kernel-source, do I have to ask
> for it, or is this done automatically? Do patches have to be signed off?
> Do I have to use dpatch?
>
To get them included in kernel-source, simply include the patches in the
patch directory, and update the appropriate patches/series file. Patches
don't have to be signed off, just make sure they don't break things
horribly. If you have patches that change stuff that isn't m68k-specific,
be sure it's solid. Patches must use dpatch.
> And how
is this "building-for-all-arches-from-one-source" going to work,
> which package is supposed to be used for that, kernel-source?
>
Yes.
> Maybe I just stay in my own little m68k directory, but there you have
> it, m68k is in. And even better, the 2.6.8 images I uploaded this
> morning are actually working on my Amiga and my Mac Quadra, so maybe, in
> the not too distant future, even m68k does not need 2.2.x anymore :-)
>
As I said before, if m68k patches aren't intrusive, they're more than
welcome directly in the kernel-source package..
Reply to: