From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3] musl: Update to 1.1.18
Date: Thu, 2 Nov 2017 14:24:15 +0200 [thread overview]
Message-ID: <e7b239be-9c34-18b1-7b63-006334d7d2db@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqKMjmPLm0yP91ojS3OX5rLkEW34uwrvR02V5rcs4VWGA@mail.gmail.com>
On 11/02/2017 02:21 PM, Otavio Salvador wrote:
> On Thu, Nov 2, 2017 at 10:19 AM, Alexander Kanavin
> <alexander.kanavin@linux.intel.com> wrote:
>> On 11/02/2017 07:39 AM, Khem Raj wrote:
>>
>>> Changes since v2: Move to 1.1.18 release
>>> -PV = "1.1.16+git${SRCPV}"
>>> +PV = "1.1.18+git${SRCPV}"
>>
>>
>> Can you drop this, and simply rename the recipe to musl_1.1.18.bb please?
>
> Why? keeping it on _git makes sense to me.
Only if it's a random development revision (e.g. 1.1.18 plus a bunch of
commits) - if the version taken is a pristine tagged release, it should
be indicated as such, regardless of whether it's taken from a tarball or
a git checkout.
Alex
next prev parent reply other threads:[~2017-11-02 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 5:39 [PATCH V3] musl: Update to 1.1.18 Khem Raj
2017-11-02 12:19 ` Alexander Kanavin
2017-11-02 12:21 ` Otavio Salvador
2017-11-02 12:24 ` Alexander Kanavin [this message]
2017-11-02 15:28 ` Khem Raj
2017-11-02 15:30 ` Alexander Kanavin
2017-11-02 16:06 ` Khem Raj
2017-11-02 16:10 ` Otavio Salvador
2017-11-02 16:15 ` Alexander Kanavin
2017-11-03 15:08 ` akuster808
2017-11-03 15:34 ` Alexander Kanavin
2017-11-03 15:48 ` Otavio Salvador
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=e7b239be-9c34-18b1-7b63-006334d7d2db@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox