From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] lttng-modules: upgrade 2.9.5 -> 2.10.4
Date: Wed, 17 Jan 2018 16:41:57 +0000 [thread overview]
Message-ID: <1516207317.29722.286.camel@linuxfoundation.org> (raw)
In-Reply-To: <2aef8a4f-9d0b-ab44-02ea-e1ad8a4e1810@linux.intel.com>
On Wed, 2018-01-17 at 17:23 +0200, Alexander Kanavin wrote:
> On 01/17/2018 05:25 PM, Richard Purdie wrote:
> >
> > LICENSE file contains a list of files and addtional files were
> > added to
> > the list, license was unchanged.
> I'd like to standardize this to a tag, and so the license change
> text
> mentions a tag. Something like Otavio did:
>
> License-checksum-change: added new contributors
>
> The idea is to make the automatic check for this more reliable so we
> don't have to ask contributors to explain the license changes all the
> time.
I'd suggest we use the form:
License-Change: Copyright years updates
which is shorter and is more similar in style to Upstream-Status: for
example...
Cheers,
Richard
next prev parent reply other threads:[~2018-01-17 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 15:25 [PATCH 1/4] nasm: upgrade 2.13.01 -> 2.13.02 Richard Purdie
2018-01-17 15:25 ` [PATCH 2/4] lttng-ust: upgrade 2.9.1 -> 2.10.1 Richard Purdie
2018-01-17 15:25 ` [PATCH 3/4] lttng-modules: upgrade 2.9.5 -> 2.10.4 Richard Purdie
2018-01-17 15:23 ` Alexander Kanavin
2018-01-17 16:41 ` Richard Purdie [this message]
2018-01-17 16:57 ` Otavio Salvador
2018-01-17 15:25 ` [PATCH 4/4] subversion: upgrade 1.9.6 -> 1.9.7 Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2018-01-17 15:22 [PATCH 1/4] nasm: upgrade 2.13.01 -> 2.13.02 Richard Purdie
2018-01-17 15:22 ` [PATCH 3/4] lttng-modules: upgrade 2.9.5 -> 2.10.4 Richard Purdie
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=1516207317.29722.286.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.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.