Re: [PATCH] Introduce git version --list-features for porcelain use

From: Junio C Hamano <junkio@cox.net>
Date: May 31, 2007, 23:46 UTC
Message-ID: <7vk5uo1rpr.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070531002030.GA15714@spearce.org>

"Shawn O. Pearce" <spearce@spearce.org> writes:

Show 22 quoted lines

> As a porcelain author I'm finding it difficult to keep track of
> what features I can use in git-gui.  Newer versions of Git have
> newer capabilities but they don't always immediately get newer
> version numbers that I can easily test for.
>
> This is a simple plumbing option that lets a porcelain ask the
> plumbing for its capabilities, at which point the porcelain can
> work around anything missing, or recommend to the user that they
> upgrade their plumbing layer.
>
> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
> ---
>
> 	Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 	>
> 	> On Wed, 30 May 2007, Alex Riesen wrote:
> 	>
> 	> > git-version --features?
> 	>
> 	> Melikes.
>
> 	Good?

Hmmm. I am not sure if you want list-features in the features list -- how are you going to test for it?

Also I still do not understand why you want redirect-stderr. Are you writing for a shell-less environment?