From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/5] distro_tracking_fields: updates for sudo, mtools, grep, and openssh
Date: Mon, 31 Oct 2011 09:08:45 +0000 [thread overview]
Message-ID: <201110310908.45138.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4EA86F93.4080407@intel.com>
On Wednesday 26 October 2011 21:37:39 Saul Wold wrote:
> > -RECIPE_TIME_BETWEEN_LAST_TWO_RELEASES_pn-sudo = "1 month"
> > -RECIPE_LATEST_RELEASE_DATE_pn-sudo = "2011/05/16"
> > +RECIPE_TIME_BETWEEN_LAST_TWO_RELEASES_pn-sudo = "2 months"
> > +RECIPE_LATEST_RELEASE_DATE_pn-sudo = "2011/10/21"
>
> These date formats should be MMM DD, YYYY also, for all the data listed
> below also.
I'd been meaning to ask this before - is there a good reason for not being
consistent and using the same format for all date fields in this file?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-31 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 21:32 [PATCH 0/5] Recipe upgrades Scott Garman
2011-10-25 21:32 ` [PATCH 1/5] sudo: upgrade to 1.8.3 Scott Garman
2011-10-25 21:32 ` [PATCH 2/5] grep: upgrade to 2.9 Scott Garman
2011-10-25 21:36 ` [PATCH 3/5] mtools: upgrade to 4.0.17 Scott Garman
2011-10-25 21:36 ` [PATCH 4/5] openssh: upgrade to 5.9p1 Scott Garman
2011-10-25 21:36 ` [PATCH 5/5] distro_tracking_fields: updates for sudo, mtools, grep, and openssh Scott Garman
2011-10-26 20:37 ` Saul Wold
2011-10-31 9:08 ` Paul Eggleton [this message]
2011-10-31 15:46 ` Saul Wold
2011-10-31 16:05 ` Koen Kooi
2011-11-01 11:38 ` Paul Eggleton
2011-10-27 7:31 ` [PATCH 0/5] Recipe upgrades Richard Purdie
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=201110310908.45138.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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