From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: New recipe for openmoko QA test scripts
Date: Tue, 03 Mar 2009 08:19:06 +0100 [thread overview]
Message-ID: <goilla$vh8$1@ger.gmane.org> (raw)
In-Reply-To: <1236023043.6800.1174.camel@alap>
On 02-03-09 20:44, Angus Ainslie wrote:
> Please review for any policy violations.
>
> Thanks
> Angus
>
> --- openembedded/packages/openmoko-projects/openmoko-qa-scripts.bb.oring 1969-12-31 17:00:00.000000000 -0700
> +++ openembedded/packages/openmoko-projects/openmoko-qa-scripts.bb 2009-03-02 12:38:55.000000000 -0700
> @@ -0,0 +1,19 @@
> +DESCRIPTION = "Openmoko QA test scripts"
> +SECTION = "utils"
> +LICENSE = "GPL"
> +PV = "gitr${SRCREV}"
NACK, as pointed out numerous times before: git revisions don't sort, so
the above breaks upgrade paths.
next prev parent reply other threads:[~2009-03-03 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 19:44 New recipe for openmoko QA test scripts Angus Ainslie
2009-03-03 4:47 ` Denys Dmytriyenko
2009-03-03 7:19 ` Koen Kooi [this message]
2009-03-05 15:26 ` 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='goilla$vh8$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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