-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/26/2011 06:26 PM, Arnaud Lacombe wrote: > Hi, > > On Sat, Feb 26, 2011 at 6:16 PM, Miguel Ojeda > <miguel.ojeda.sandonis@xxxxxxxxx> wrote: >> On Sat, Feb 26, 2011 at 11:57 PM, Arnaud Lacombe <lacombar@xxxxxxxxx> wrote: >>> On Sat, Feb 26, 2011 at 5:47 PM, Miguel Ojeda >>> <miguel.ojeda.sandonis@xxxxxxxxx> wrote: >>>> /proc/config.gz is provided by the kernel and its format is defined by >>>> kconfig itself which is, as well, part of the kernel (it is not one >>>> random format from a pool of a trillion), so it will be nice if >>>> kconfig learns how to read its own configuration from there. >>>> >>> your point being ? kconfig is not only used by the Linux kernel, and >>> you cannot expect the feature to only be used in the cozy Linux kernel >>> environment. >> >> My point was that supporting reading from a .gz file is not anywhere >> near "knowing about the trillion file format which exist in the world" >> > Well, Jeff's patch is already about gzip and bzip2. Soon it will be > compress, xz, zip, rar, then rzip, lzma, 7z ... I added bzip2 as an exercise. But realistically, what would be wrong with distributors deciding to ship /boot/config-$UNAME_RELEASE.bz2 and saving a bit of valuable /boot disk space? Even if people /do/ submit patches do do all of those formats, your argument is based on the premise that having that ability is necessarily bad. I don't think we need them, but I don't think it's a good argument against this patch either. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1pjxIACgkQLPWxlyuTD7Jm3wCfSG6z1aBOT6PDLVmQeycW5mmM Z/IAoJJXW7P5C+cWg8lFSTmm+HtBjR0E =b5Hc -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
