I think you are ignoring the fact that this clause (#3) in the GPL only
relates only if "you copy or distribute the Program (or a work based on
it, under Section 2) in object code or executable form".
> >There are still lots of other ways to get the kernel source.
>
> You are using the conventional meaning of "source code", which is
> roughly, "whatever you compile to get the executable". However, this
> is not the "source" for GPL purposes. For GPL purposes, the source is
> the preferred form of a work for purposes of modifying it.
>
> This means you can't remove meta information that's useful for
> modifying because that is not the preferred form. Such meta
> information includes whatever is useful for modifying it, such as
> revision history and chain of custody.
>
> You can't have two "source"s, one a private repository that you
> prefer to use for making changes and the other an "obfuscated" public
> version you distribute for GPL compliance which is missing all the
> other useful information.
>
> Checking source out of a repository, separating away the revision
> history, is an obfuscatory act. The GPL prohibits such source
> obfuscation and requires you to distribute the source in whatever is
> the actual preferred form for modifying it. Really. Sorry.
Again you are ignoring the fact that there are other methods by which
the source code is available in the "preferred form", just not quite as
timely as directly from the BK repository (which is itself in a form, SCCS,
which does not require BK to access), and there is nothing in the GPL which
requires that the source be made avaible instantly.
Cheers, Andreas
-- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/