From: "Mike \(mwester\)" <mwester@dls.net>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: tzdata.bb
Date: Fri, 2 Mar 2007 22:43:09 -0600 [thread overview]
Message-ID: <08fa01c75d4e$71e4a2b0$6e01a8c0@twilight> (raw)
In-Reply-To: f34f85580702070514u42b2b887qf416466c5b7bf83d@mail.gmail.com
tzdata (and tzcode-native) are committed.
The tzdata recipe is Todd's original, I incorporated the feedback from the
list (and added any bugs). The tzcode-native recipe provides the native
timezone utilities, including zic.
Regards,
Mike (mwester)
----- Original Message -----
From: "Todd Blumer" <sdgvulpes@gmail.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: "Rene Wagner" <rw@handhelds.org>
Sent: Wednesday, February 07, 2007 7:14 AM
Subject: [oe] tzdata.bb
> Because of the impending changes to daylight savings time (DST) here
> in the US, I was motivated to work on creating a new timezone package.
> In the base package I tried to put a city in every timezone around the
> world. This package replaces the 'timezone' package used by Opie, so
> some other packages will need to be changed to depend on tzdata
> instead of timezone. (I used 'tzdata' since that is the Debian name
> and in case some developers were not ready to switch over to tzdata.)
>
> Someone with write access to oe (something I should probably get
> eventually :-) can commit this to dev if you feel it is appropriate to
> do so. I have tested the US Eastern time.
>
> I'm sure more work could be done here. Feedback is welcome.
> --
> Todd Blumer
> SDG Systems
next prev parent reply other threads:[~2007-03-03 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 13:14 tzdata.bb Todd Blumer
2007-02-07 13:22 ` tzdata.bb Koen Kooi
2007-02-07 14:42 ` tzdata.bb Todd Blumer
2007-02-08 1:43 ` tzdata.bb Matt Reimer
2007-02-10 18:02 ` tzdata.bb Mike (mwester)
2007-03-03 4:43 ` Mike (mwester) [this message]
2007-03-14 22:14 ` tzdata.bb Hans Henry von Tresckow
2007-03-20 13:09 ` tzdata.bb Todd Blumer
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='08fa01c75d4e$71e4a2b0$6e01a8c0@twilight' \
--to=mwester@dls.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.