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 (Jul 2009, #03; Wed, 29)
Date: Wed, 29 Jul 2009 17:50:46 -0700 (PDT) [thread overview]
Message-ID: <m3vdlb0zb6.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vzlanqj9p.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
>
> There may have been updates during 1.6.4-rc period that I missed.
There weren't any updates. I plan on replacing the 4 top patches soon
(without '-partial_query' one, as it would not be needed), less proof
of concept, but still RFC.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-07-30 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 21:19 What's cooking in git.git (Jul 2009, #03; Wed, 29) Junio C Hamano
2009-07-29 22:46 ` cc/sequencer-rebase-i, was " Johannes Schindelin
2009-07-30 0:50 ` 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=m3vdlb0zb6.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 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 NNTP newsgroup(s).