From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] tzdata/tzcode: leave only latest version
Date: Fri, 9 Apr 2010 09:38:52 +0200 [thread overview]
Message-ID: <20100409073852.GH3269@jama> (raw)
In-Reply-To: <1270797788-25090-1-git-send-email-khimov@altell.ru>
On Fri, Apr 09, 2010 at 11:23:07AM +0400, Roman I Khimov wrote:
> I don't see any value in old tzdata/tzcode-native recipes as tzcode is only
> used to compile tzdata and compiled tzdata should be compatible with any
> version of glibc and it's good to have it latest. So I think we should only
> leave latest tzdata version and move that forward whenever someone discovers
> that elsie.nci.nih.gov dropped that version. Same for tzcode.
>
> Add comments to unconditionally move that versions forward whenever there is
> a new release.
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
prev parent reply other threads:[~2010-04-09 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 9:30 [PATCH 0/2] Updates to tzcode-native and tzdata Antonio Ospite
2010-04-08 9:30 ` [PATCH 1/2] tzcode-native_2010f: Update tzdata SRC_URI and checksum Antonio Ospite
2010-04-08 10:14 ` Martyn Welch
2010-04-08 10:15 ` Roman I Khimov
2010-04-08 10:28 ` Roman I Khimov
2010-04-08 19:11 ` Roman I Khimov
2010-04-08 19:18 ` Antonio Ospite
2010-04-08 9:30 ` [PATCH 2/2] tzdata: move tzdata_2010g.bb to tzdata_2010h.bb Antonio Ospite
2010-04-08 10:24 ` Roman I Khimov
2010-04-08 10:28 ` [PATCH 0/2] Updates to tzcode-native and tzdata Roman I Khimov
2010-04-09 7:23 ` [PATCH 1/2] tzdata/tzcode: leave only latest version Roman I Khimov
2010-04-09 7:23 ` [PATCH 2/2] preferred-om-2008-versions.inc: use latest tzcode-native/tzdata Roman I Khimov
2010-04-09 7:39 ` Martin Jansa
2010-04-09 7:38 ` Martin Jansa [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=20100409073852.GH3269@jama \
--to=martin.jansa@gmail.com \
--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