Hi, The changelist files take new names with every version and then get updated. These files do not have license headers (like the other old files) but they were part of the pre-Apache life of MADlib. I believe the confusion originates from using the regular "mv" command instead of "git mv".
Thanks, Orhan On Thu, Sep 8, 2016 at 4:23 PM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > The MADlib community is unclear on how to deal with the dual license. > > Well that makes two off us. :-) > > > Till now we've treated all *new* files (i.e. files that were created > > after joining Apache) as Apache license with required headers and all > > old files under the BSD. > > I can see several new files that don’t have Apache headers. For example > incubator-madlib-1.9.1/src/madpack/changelist_*_1.9.1.yaml > > > Is it recommended that we add the Apache header on any file that > > contains an edit (old or new)? > > The advice here [1] (see points 4 and 5) say only if the changes are > significant but it assumes that files have a license header in the first > place. > > Thanks, > Justin > > 1.http://www.apache.org/legal/src-headers.html#3party > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
