From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
"John 'Warthog9' Hawley" <warthog9@eaglescrag.net>,
Kevin Cernekee <cernekee@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2011, #07; Wed, 27)
Date: Thu, 28 Apr 2011 12:39:02 -0700 (PDT) [thread overview]
Message-ID: <m37haew4io.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v1v0n75rj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> What's cooking in git.git (Apr 2011, #07; Wed, 27)
> --------------------------------------------------
> [New Topics]
> * ft/gitweb-tar-with-gzip-n (2011-04-26) 1 commit
> (merged to 'next' on 2011-04-26 at 8e59a0e)
> + gitweb: supply '-n' to gzip for identical output
>
> Will merge to "master" by the end of week #2.
Nice.
> --------------------------------------------------
> [Stalled]
>
> * jn/gitweb-js (2011-04-15) 13 commits
> - gitweb: Make JavaScript ability to adjust timezones configurable
> - gitweb.js: Add UI for selecting common timezone to display dates
> - gitweb: JavaScript ability to adjust time based on timezone
> - gitweb: Unify the way long timestamp is displayed
> - gitweb: Refactor generating of long dates into format_timestamp_html
> - gitweb.js: Provide getElementsByClassName method (if it not exists)
> - gitweb.js: Introduce gitweb/static/js/lib/cookies.js
> - gitweb.js: Extract and improve datetime handling
> - gitweb.js: Provide default values for padding in padLeftStr and padLeft
> - gitweb.js: Update and improve comments in JavaScript files
> - gitweb: Split JavaScript for maintability, combining on build
> - Remove gitweb/gitweb.cgi and other legacy targets from main Makefile
> - git-instaweb: Simplify build dependency on gitweb
>
> I do not recall seeing this series much reviewed. Is everybody happy with
> this series?
I have just resend this series in cleaned up form, containing all the
fixes and extra patches; in fact nearly the same as 'jn/gitweb-js'
branch. It includes comparison to J.H. patch.
I think it addresses all the issues Kevin and you found with previous
versions; I haven't heard from J.H. yet.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2011-04-28 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 21:18 What's cooking in git.git (Apr 2011, #07; Wed, 27) Junio C Hamano
2011-04-28 19:39 ` Jakub Narebski [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=m37haew4io.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=cernekee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=warthog9@eaglescrag.net \
/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.