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 (Aug 2009, #06; Sun, 30)
Date: Tue, 01 Sep 2009 09:47:11 -0700 (PDT) [thread overview]
Message-ID: <m37hwili5q.fsf@localhost.localdomain> (raw)
In-Reply-To: <7viqg48nxi.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jn/gitweb-blame (2009-08-06) 3 commits
> - gitweb: Create links leading to 'blame_incremental' using JavaScript
> - gitweb: Incremental blame (WIP)
> - gitweb: Add optional "time to generate page" info in footer
>
> Ajax-y blame WIP
There is replacement series sent to git mailing list a little while
ago.
The replacements for "time to generate page" and 'blame_incremental'
are IMVHO out of WIP (but more testing, in different web browsers
would be good).
The part that actualy creates links that lead to 'blame_incremental'
view is still work in progress, and needs ideas how to correctly
implement it.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-09-01 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 7:03 What's cooking in git.git (Aug 2009, #06; Sun, 30) Junio C Hamano
2009-08-31 9:32 ` Johan Herland
2009-09-01 5:58 ` stash --dwim safety (was Re: What's cooking in git.git (Aug 2009, #06; Sun, 30)) Junio C Hamano
2009-09-01 6:27 ` stash --dwim safety Matthieu Moy
2009-09-01 6:57 ` Jeff King
2009-09-02 4:11 ` Junio C Hamano
2009-09-02 4:59 ` Jeff King
2009-09-02 6:48 ` Johannes Schindelin
2009-09-02 6:26 ` Matthieu Moy
2009-09-01 15:08 ` What's cooking in git.git (Aug 2009, #06; Sun, 30) Peter Krefting
2009-09-01 16:47 ` Jakub Narebski [this message]
2009-09-01 16:51 ` Junio C Hamano
2009-09-02 17:44 ` Jakub Narebski
2009-09-02 18:16 ` Peter Harris
2009-09-01 22:25 ` Nick Edelen
2009-09-02 5:32 ` 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=m37hwili5q.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.