All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: akuster808 <akuster808@gmail.com>,
	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: Fri, 3 Nov 2017 17:34:33 +0200	[thread overview]
Message-ID: <daa2889c-e7cc-a1e8-fb25-7df9bc3d2e3d@linux.intel.com> (raw)
In-Reply-To: <8a2910bb-d958-60e6-a04d-ce7593c4b83b@gmail.com>

On 11/03/2017 05:08 PM, akuster808 wrote:

> SRCPV causes package versioning havoc. You can not tell what version
> 1.1.8+git(hash)  or 1.1.8+git(hash) is the latest on a system. Can your
> package manage figure that out?

I thought the entire point of SRCPV is to provide something that is 
guaranteed to increase over time? It makes sense when taking random 
revisions from git, but when git is used only for tagged releases, it's 
just annoying visual clutter.

Alex


  reply	other threads:[~2017-11-03 15:34 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
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 [this message]
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=daa2889c-e7cc-a1e8-fb25-7df9bc3d2e3d@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=akuster808@gmail.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 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.