Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Martin Siegumfeldt <mns@gomspace.com>,
	Khem Raj <raj.khem@gmail.com>,
	Paul Cercueil <paul@crapouillou.net>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	Christian Eggers <ceggers@arri.de>
Subject: Re: [meta-oe][PATCH 1/2] libiio: update to version 0.25
Date: Wed, 12 Jul 2023 09:25:56 +0200	[thread overview]
Message-ID: <581dd812-873e-eb56-50cc-7b03de57799a@denx.de> (raw)
In-Reply-To: <AM0PR09MB3988DFDE6AFBFBF4A7DF5078AF36A@AM0PR09MB3988.eurprd09.prod.outlook.com>

On 7/12/23 08:40, Martin Siegumfeldt wrote:
> On Tue, Jul 11, 2023 at 6:11 PM Marek Vasut <marex@denx.de> wrote:
>>
>> The version 0.25 has been released, it has not been tagged however.
>> Update the this version anyway.
> 
> hmm how do we know where to peg SRCREV ? I wonder if we should wait
> for tag to appear.

The 0.24 appeared on matching commit
"CMake: Bump version to v0.24"
Same for 0.23, 0.22, 0.21. 0.20 was not tagged like this 0.25. 0.19 was 
tagged again etc.

I think it is safe to assume the tag was just missed or not pushed, but 
I planned to ping Paul about it. Might as well add Paul to CC help and 
ask that way.

Paul, is the libiio 0.25 tag just missing ?

> I agree in waiting for tag to be published.

See above.

> Also, would it make sense to rename the recipe file according to the actual version rather than 'git'? In the past I think the recipe referred arbitrary git commits, however we have moved to referring actual release commits now.

Yes, good point, but that's a separate patch. I made a local commit so 
it isn't forgotten.


  reply	other threads:[~2023-07-12  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  1:11 [meta-oe][PATCH 1/2] libiio: update to version 0.25 Marek Vasut
2023-07-12  1:11 ` [meta-oe][PATCH 2/2] libiio: enable c++ bindings Marek Vasut
2023-07-12  4:13 ` [meta-oe][PATCH 1/2] libiio: update to version 0.25 Khem Raj
2023-07-12  6:40   ` Martin Siegumfeldt
2023-07-12  7:25     ` Marek Vasut [this message]
     [not found]       ` <179dcdfa3b51fc0b7b7426f041fd23bb17ebfa17.camel@crapouillou.net>
2023-07-12  7:44         ` Marek Vasut
2023-07-12 16:14     ` Khem Raj

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=581dd812-873e-eb56-50cc-7b03de57799a@denx.de \
    --to=marex@denx.de \
    --cc=ceggers@arri.de \
    --cc=mns@gomspace.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul@crapouillou.net \
    --cc=raj.khem@gmail.com \
    /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