From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SRCPV migration
Date: Mon, 16 Nov 2009 11:59:10 +0100 [thread overview]
Message-ID: <hdrb9v$1dp$1@ger.gmane.org> (raw)
In-Reply-To: <1258368570.5799.99.camel@dax.rpnet.com>
On 16-11-09 11:49, Richard Purdie wrote:
> On Mon, 2009-11-16 at 11:37 +0100, Koen Kooi wrote:
>> So basically every recipe that is using SRCPV in PV or PR is unsuitable
>> to be put in online feeds. That should be enough to stop the SRCPV merge
>> into .dev.
>
> How is this different to the current situation though?
In the current situation (actually, last weeks situation) SRCPV was
never used.
> If SRCREV is locked down you will get 1 as the local build revision back
> and it will not change and will be the same for everyone.
> If its not locked down, all bets are off but they always have been - no
> change.
Ah, that was the bit of info I was missing. But if SRCREV is locked down
(as it should!) what's the point of putting SRCPV in PV or PR? It seems
to make things worse if you update a locked SRCREV, since SRCPV will
remain '1'.
regards,
Koen
next prev parent reply other threads:[~2009-11-16 11:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 16:36 SRCPV migration Martin Jansa
2009-11-15 21:22 ` Martin Jansa
2009-11-16 8:38 ` Koen Kooi
2009-11-16 9:39 ` Richard Purdie
2009-11-16 10:37 ` Koen Kooi
2009-11-16 10:49 ` Richard Purdie
2009-11-16 10:59 ` Koen Kooi [this message]
2009-11-16 11:39 ` Richard Purdie
2009-11-16 12:10 ` Koen Kooi
2009-11-16 12:37 ` Richard Purdie
2009-11-16 13:15 ` Koen Kooi
2009-11-16 13:43 ` Martin Jansa
2009-11-16 13:55 ` Richard Purdie
2009-11-17 8:55 ` Martin Jansa
2009-11-17 9:08 ` Phil Blundell
2009-11-17 10:01 ` Richard Purdie
2009-11-17 10:57 ` Martin Jansa
2009-11-20 10:20 ` Martin Jansa
2009-11-17 10:18 ` mok
2009-11-17 15:12 ` Martin Jansa
2009-11-17 16:23 ` Martin Jansa
2009-11-17 16:53 ` Martin Jansa
2009-11-17 15:49 ` Henning Heinold
2009-11-17 9:42 ` Martin Jansa
2009-11-19 16:02 ` Koen Kooi
2009-11-19 16:11 ` Martin Jansa
2009-11-19 16:34 ` Martin Jansa
2009-11-19 17:34 ` Koen Kooi
2009-11-16 11:51 ` Martin Jansa
2009-11-16 12:19 ` Koen Kooi
2009-11-16 12:39 ` Martin Jansa
2009-11-16 10:42 ` Holger Hans Peter Freyther
2009-11-22 19:05 ` SRCPV migration - How SRCPV works! Martin Jansa
2009-11-23 8:07 ` Koen Kooi
2009-11-23 8:52 ` Martin Jansa
2009-11-23 11:12 ` Koen Kooi
2009-11-23 11:42 ` Martin Jansa
2009-11-23 12:00 ` Richard Purdie
2009-11-23 12:15 ` Richard Purdie
2009-11-23 12:29 ` Philip Balister
2009-11-23 13:24 ` Koen Kooi
2009-11-23 13:31 ` Koen Kooi
2009-11-23 13:52 ` Otavio Salvador
2009-11-23 14:58 ` Koen Kooi
2009-11-23 15:09 ` Martin Jansa
2009-11-23 14:29 ` Richard Purdie
2009-11-23 15:00 ` Koen Kooi
2009-11-23 15:12 ` Martin Jansa
2009-11-23 15:52 ` Koen Kooi
2009-11-23 16:07 ` Martin Jansa
2009-11-23 15:05 ` Philip Balister
2009-11-23 15:47 ` Chris Conroy
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='hdrb9v$1dp$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox