From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] timezone:upgrade 2019b -> 2019c
Date: Fri, 13 Sep 2019 18:03:51 +0300 [thread overview]
Message-ID: <20190913150351.GA5554@localhost> (raw)
In-Reply-To: <95697dfd-5692-c175-3fd4-0609e3b96310@gmail.com>
On Thu, Sep 12, 2019 at 10:30:30AM -0700, akuster808 wrote:
> On 9/12/19 7:28 AM, Adrian Bunk wrote:
>...
> I applaud those who take the time and effort of providing additional
> information in the commit messages.
>...
Blind pasting of the complete upstream changelog is not exactly an
effort that would warrant applause.
A short summary of the relevant parts might be useful, but when you are
asking to include details like
The 1892-05-01 transition in Brussels was at 00:17:30, not at noon.
that's only adding noise in "git log".
> > 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,
I am also 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?
Backporting does not make a difference here,
it is about under what licence the contents of the commit message is.
Pasting texts from elsewhere makes the licencing of the git metadata a
complete mess, like you cannot claim it is MIT if it contains text from
GPLv3 software.
A person using Signed-off-by also certifies that the whole contribution
is under an open source license, which would make pasting changelogs from
components that are not under an open source license clearly off-limits.
Not sure how much actual lawyers care about such issues,
but once something is in the git history it is too late.
> - armin
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-09-13 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 6:52 [PATCHv2] timezone:upgrade 2019b -> 2019c Zang Ruochen
2019-09-12 14:10 ` akuster808
2019-09-12 14:28 ` Adrian Bunk
2019-09-12 17:30 ` akuster808
2019-09-13 15:03 ` Adrian Bunk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190913150351.GA5554@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.