On 9/12/19 7:28 AM, Adrian Bunk wrote: > On Thu, Sep 12, 2019 at 07:10:08AM -0700, akuster808 wrote: >> >> On 9/11/19 11:52 PM, Zang Ruochen wrote: >>> -tzdata : upgrade from 2019b to 2019c. >>> >>> -tzcode-native : upgrade from 2019b to 2019c. >>> >>> -tzdata.bb and tzcode-native.bb require timezone.inc. >> Not exactly what I had in mind. When there is a TZ update they send out >> what changed any why. It looks like this" >> ... > IMHO that would be far too long for a commit message,
I have been including that information for years. IMHO that make it the standard for that package. Up until now , no one has had an issue with it. > and changelogs of this size would make the git history > unreadable if everyone would start pasting huge upstream > changelogs in their commits. I have no fear of that ever happening as it has been totally acceptable not to have a commit message included and there is no enforcement of that process. We had this discussion in the past and we go round and round and nothing ever changes. So I am not worried. I applaud those who take the time and effort of providing additional information in the commit messages. > cu > Adrian > > BTW: How is the legal handling of the metadata, when such lengthy > 3rd party texts copyrighted by various people under various > licences are distributed as part of the git metadata? Interesting question. Since I am not a lawyer, maybe you can help guide the community so we do the right thing. Now I am worried about the stable branches, do backports have this same issue, are those 3-party texts? - armin > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
