Mailinglist Archive: opensuse-kernel (131 mails)

[0bo0 <0.bugs.only.0@xxxxxxxxx>]

On Sun, Feb 7, 2010 at 1:09 PM, Jan Engelhardt <jengelh@xxxxxxxxxx> wrote:
> Well, the hash code nature actually allows a party to download
> single bits. The top commit, root dir listing, fs/ listing,
> > You make a diff between kernel_a:fs/btrfs/ and btrfs_clone:fs/btrfs/,
> and apply that on top of the suse one.

I'll give that a try.

> And *praying* that the new
> code does not rely on an incompatible change of a struct foo that
> the rest of the old kernel depends on at the same time!

Clear.  Which is why I'd asked on this list a couple of days ago
whether an opensuse/obs repo tracking the btrfs-unstable changes
already exists.  that'd be preferable ...  Lots of useful changes
(e.g., additional btrfsctl options in the tools, etc) are being rolled
into the unstable tree, but not promoted to the stable one that, i
think, opensuse Kernel:HEAD builds track.

I'm not interested in yet another "just use the vanilla kernels"
discussion@ irc, lists, etc -- and would much prefer to stay with
*suse built/managed kernel development.

Thanks.
-- 
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx