Re: What's in git.git

From: Jakub Narebski <jnareb@gmail.com>
Date: Oct 26, 2006, 09:12 UTC
Message-ID: <ehpu4t$ch2$1@sea.gmane.org>
In-Reply-To: <7vk62npipb.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 6 quoted lines

> * The 'master' branch has these since the last announcement.
> 
>   I've flushed all the 'gitweb/' changes from "next" and core
>   support that some of them needed; notably "for-each-ref" and
>   "blame --porcelain" is now in "master".  Oh, and "annotate"
>   is now a mere synonym for "blame -c".

[...]

>    Junio C Hamano (20):

[...]

>       gitweb: prepare for repositories with packed refs.

[...]

>       gitweb: use for-each-ref to show the latest activity across branches

This unfortunately means that I cannot test gitweb based on 'master' branch using _released_ git core, git version 1.4.3.3, as it doesn't have git-for-each-ref nor git-show-ref.

BTW. do people often use latest gitweb with older git binaries? Should we try to wait for core feature to mature to released version before using it in gitweb? Or perhaps we should add some kind of version checking, and provide workrounds, e.g. using $ENV{GIT_DIR} if git core doesn't support --git-dir option, pathlimit filtering using git-rev-list piped to git-diff-tree --stdin in git_history if there is no --full-history option, show always HEAD activity if there is no git-for-each-ref etc.; well the latest we can do without checking for git core version, just

        if -x qx($GIT --exec-path)/git-for-each-ref

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git