From: Junio C Hamano <gitster@pobox.com>
To: Ciaran <ciaranj@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: What's cooking in git.git (May 2011, #04; Sun, 8)
Date: Mon, 16 May 2011 13:19:33 -0700 [thread overview]
Message-ID: <7vk4dql7oq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <BANLkTimz5KpSC04gQkYL+oXJu5JfR8t8nw@mail.gmail.com> (Ciaran's message of "Mon, 9 May 2011 09:55:58 +0100")
Ciaran <ciaranj@gmail.com> writes:
>> * jn/gitweb-js (2011-04-28) 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 code to handle cookies from JavaScript
>> - 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
>
> Sorry if this is dumb, as I'm unsure how Git (the mailing list)
> handles regression tracking, but I saw no mention of this thread:
> http://marc.info/?l=git&m=130445013906259&w=2
I did not recall any regression in gitweb JavaScript support topic
reported, so I was puzzled about the above quote.
I am aware of an issue around the merge-recursive area reported by you on
May 3rd (Message-ID: <BANLkTimcRbuYzSp+MM-vsvxoWhAS8Jvo8Q@mail.gmail.com>,
$gmane/172617) [*1*]. I had an impression that the guilty party pointed at
by the bisection was already looking into it.
Elijah, any progress on that one?
[Footnote]
*1* This is just my preference but I'd be happier if you gave the
Message-Id of the message; it would be easier to find the thread. A
reference to marc.info to me means an extra "launch browser only to look
at it" and tends to be backburnered when I am busy (and I usually am).
next prev parent reply other threads:[~2011-05-16 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 5:33 What's cooking in git.git (May 2011, #04; Sun, 8) Junio C Hamano
2011-05-09 8:55 ` Ciaran
2011-05-16 20:19 ` Junio C Hamano [this message]
2011-05-18 3:57 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vk4dql7oq.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ciaranj@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).