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 (Mar 2009, #01; Tue, 03)
Date: Tue, 03 Mar 2009 01:21:35 -0800 (PST) [thread overview]
Message-ID: <m3r61ft10q.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vprgzdlom.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> ----------------------------------------------------------------
> [Stalled and may need help and prodding to go forward]
>
> * gb/gitweb-base (Sun Feb 15 10:18:36 2009 +0100) 1 commit
> - gitweb: fix wrong base URL when non-root DirectoryIndex
Errrr... isn't this already in 'master' as v1.6.2-rc1-3-g81d3fe9 ?
> * jc/blame (Wed Jun 4 22:58:40 2008 -0700) 2 commits
> + blame: show "previous" information in --porcelain/--incremental
> format
> + git-blame: refactor code to emit "porcelain format" output
>
> This gives Porcelains (like gitweb) the information on the commit _before_
> the one that the final blame is laid on, which should save them one
> rev-parse to dig further. The line number in the "previous" information
> may need refining, and sanity checking code for reference counting may
> need to be resurrected before this can move forward.
>
> I thought recent tig discussion may blow new life into it, but is this
> unneeded? If so I'd rather revert it (or discard after 1.6.2).
This would be nice to have for gitweb.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-03-03 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 9:01 What's cooking in git.git (Mar 2009, #01; Tue, 03) Junio C Hamano
2009-03-03 9:15 ` Jeff King
2009-03-16 4:53 ` Junio C Hamano
2009-03-17 7:51 ` Jeff King
2009-03-03 9:21 ` Jakub Narebski [this message]
2009-03-03 11:11 ` Johannes Schindelin
2009-03-05 6:43 ` Christian Couder
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=m3r61ft10q.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).