From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2011, #01; Sun, 3)
Date: Mon, 04 Apr 2011 02:16:26 -0700 (PDT) [thread overview]
Message-ID: <m3aag64bt5.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v62quc464.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'pu' while commits prefixed with '+' are in 'next'.
>
> Hopefully we will have 1.7.5-rc1 coming Wednesday.
> --------------------------------------------------
> [Cooking]
> * jh/gitweb-localtime (2011-03-23) 1 commit
> - gitweb: javascript ability to adjust time based on timezone
I am slowly working on this, but for various reasons most probably
I wouldn't have time to finish it before 8th April at earliest.
The split series would look something like this:
- gitweb: Split JavaScript for maintability, combining on build
- gitweb: Introduce and use format_timestamp
- gitweb.js: Cookies library
- gitweb.js: Parse W3CDTF date (ISO-8601 variant), format in RFC-2822
- gitweb: javascript ability to adjust time based on timezone
BTW I guess that
[PATCH (BUGFIX)] gitweb: Fix parsing of negative fractional timezones in JavaScript
Message-Id: <20110401190239.9686.12000.stgit@localhost.localdomain>
http://article.gmane.org/gmane.comp.version-control.git/170606
didn't made it into this "What's cooking..." because it was send too
late (2011-04-01 19:06:28 GMT), isn't it?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-04-04 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 23:21 What's cooking in git.git (Apr 2011, #01; Sun, 3) Junio C Hamano
2011-04-04 7:21 ` Jens Lehmann
2011-04-04 9:16 ` Jakub Narebski [this message]
2011-04-04 15:11 ` Junio C Hamano
2011-04-04 10:40 ` Michael J Gruber
2011-04-04 15:09 ` Junio C Hamano
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=m3aag64bt5.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.