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, #02; Wed, 12)
Date: Fri, 14 Aug 2009 15:27:02 -0700 (PDT) [thread overview]
Message-ID: <m3k516nic0.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vtz0co3xe.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * mr/gitweb-xz (Thu Aug 6 10:28:25 2009 -0400) 3 commits
> - gitweb: add support for XZ compressed snapshots
> - gitweb: update INSTALL regarding specific snapshot settings
> - gitweb: support to globally disable a snapshot format
>
> This should be safe as long as it does not silently enable itself for
> folks who merely updated gitweb to this version without explicitly asking
> for the new format (but I do not remember if that is what the patch does).
The latest version (v5, from 6.08) has XZ compressed snapshot ('txz')
disabled by default.
> * zf/maint-gitweb-acname (Sun Aug 2 09:42:24 2009 +0200) 1 commit
> - gitweb: parse_commit_text encoding fix
Good.
> * jn/gitweb-blame (Thu Aug 6 19:11:52 2009 +0200) 14 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
> + Revert the four topmost commits from jn/gitweb-blame topic
> + 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
>
> I haven't picked up Jakub's replacement to the second one from the tip.
> We probably should merge up to "Use light/dark" (aef3768) to 'master' and
> start the rest over.
That would be good idea.
[...]
What about 'gitweb: fix variable scoping issue in git_get_projects_list'
latest version of patch, adding (re)declaring $project_maxdepth,
$projectroot as global variables using our? Or are you waiting for
response of our resident Perl expert: Randal L. Schwartz (merlyn)?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-08-14 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 2:14 What's cooking in git.git (Aug 2009, #02; Wed, 12) Junio C Hamano
2009-08-14 22:27 ` Jakub Narebski [this message]
2009-08-15 1:51 ` Junio C Hamano
2009-08-15 7:09 ` jc/shortstatus (was: What's cooking in git.git (Aug 2009, #02; Wed, 12)) Jeff King
2009-08-15 8:18 ` jc/shortstatus Junio C Hamano
2009-08-15 8:45 ` jc/shortstatus Jeff King
2009-08-15 21:23 ` jc/shortstatus 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=m3k516nic0.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.