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, #01; Wed, 05)
Date: Thu, 06 Aug 2009 01:24:24 -0700 (PDT) [thread overview]
Message-ID: <m3vdl1pcyb.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v8whxx6gx.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * jn/gitweb-blame (Sat Jul 25 00:44:10 2009 +0200) 10 commits
> + gitweb: Create links leading to 'blame_incremental' using
> JavaScript
> + gitweb: Incremental blame (proof of concept)
> + gitweb: Add optional "time to generate page" info in footer
> + gitweb: Add -partial_query option to href() subroutine
> + gitweb: Use light/dark for class names also in 'blame' view
> + gitweb: Add author initials in 'blame' view, a la "git gui blame"
> + gitweb: Mark commits with no "previous" in 'blame' view
> + gitweb: Use "previous" header of git-blame -p in 'blame' view
> + gitweb: Mark boundary commits in 'blame' view
> + gitweb: Make .error style generic
>
> Will merge soon.
Actually I'd rather only the first part (the 'blame' view
improvements) were merged.
The 'blame_incremental' part is still in flux; I'll send in a while
next iteration of it. Currently most important part is that
"Incremental blame (proof of concept)" turns off sending
application/xhtml+xml because my browser (Firefox up to 1.5) turned on
strict mode also for JavaScript, which means no innerHTML. Also there
are quite a few items on the TODO list...
I'm sorry that I haven't made it clear. I should have send those two
parts as a separate series, in separate threads.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-08-06 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 22:04 What's cooking in git.git (Aug 2009, #01; Wed, 05) Junio C Hamano
2009-08-06 8:24 ` 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=m3vdl1pcyb.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.