[Bf-committers] GPL header...
jambay9 at gmail.com
Mon Feb 18 10:54:32 CET 2019
Thank you for confirming standard practice. I was getting a bit giddy about
ripping and stripping some code and thought, gee, would be nice to trim
that off the top :) wink and a nod.
Additionally there are some scripts that have owners copyright only; expect
those will be of limited use/distribution.
P.S. good to see mail list back in operation.
On Sun, Feb 17, 2019 at 3:05 PM Bassam Kurdali <bassam at urchn.org> wrote:
> Thanks Brecht, I like this simple rule. That way even if you only have
> one file (and don't know where it came from) you can still know the
> On Sun, 2019-02-17 at 20:26 +0100, Brecht Van Lommel wrote:
> > The convention is to always use the full license header when the code
> > is
> > under that license, regardless of the size of the file.
> > There's no alternative shorter header that we use, better to keep the
> > rule
> > about license headers simple & clear.
> > On Thu, Feb 14, 2019 at 2:57 AM Jim Bates <jambay9 at gmail.com> wrote:
> > > seen a few files w/o header, and some that it's close to 10% of the
> > > script.
> > >
> > > my question is: can this be treated as an external link/ref so not
> > > an
> > > inline block of comments?
> > >
> > > This may have been brought up before but I'm just getting back to
> > > Blender
> > > "add-on" stuff.
> > > _______________________________________________
> > > Bf-committers mailing list
> > > Bf-committers at blender.org
> > > https://lists.blender.org/mailman/listinfo/bf-committers
> > >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers