From: Saul Wold <saul.wold@intel.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: erroneously marked packages
Date: Wed, 04 Jul 2012 06:53:56 -0700 [thread overview]
Message-ID: <4FF44AF4.9080007@intel.com> (raw)
In-Reply-To: <CAJ2CSBu1HFggNOqVQt4jnH6_swNmUa5T+RrWf06h-epcNBkbuA@mail.gmail.com>
On 07/04/2012 05:26 AM, Damian, Alexandru wrote:
> Hi Saul,
>
> Some packages don't need upgrade, even if they are in the list, because
> the detection was wrong.
>
> How do we handle those ?
> I'm talking here about:
> - u-boot-mkimage, the 2012.04.1 version is already in the tree
> - js, the 1.6 (target) is older than current version
> - mobile-broadband-provider-info, target 20090309 is older than current
> version
>
It may be my list is out of date.
If it is already updated because someone else did it then my list is
olde, then you can ignore it and the next milestone list will reflect
that it's already updated, such as u-boot-mkimage.
If there a reason why we can't upgrade then you use the
NO_UPGRADE_REASON_pn-<PN> tag.
>
> Alex
prev parent reply other threads:[~2012-07-04 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:26 erroneously marked packages Damian, Alexandru
2012-07-04 13:53 ` Saul Wold [this message]
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=4FF44AF4.9080007@intel.com \
--to=saul.wold@intel.com \
--cc=alexandru.damian@intel.com \
--cc=openembedded-core@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