Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
>
> On Tue, 29 May 2007, Shawn O. Pearce wrote:
>
> > Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
> > >
> > > With this option, stderr is redirected to stdout. The short option is '-2'.
> > >
> > > Alternatively, you can say '--redirect-stderr=<filename>' to redirect
> > > stderr to a file.
> >
> > Yes, that works nicely. ;-)
> >
> > Now here's my other problem: How does git-gui know the underlying
> > git will accept --redirect-stderr? Or that it supports any other
> > recent features we've developed?
>
> I thought that git-gui is now really closely coupled with core-git.
Not really. It requires 1.5.0 and later, but after that it should
be OK with any 1.5.x version of Git. Junio graciously bundles it
with core Git, to help it get a wider audience. ;-)
However I'd like to let it be smarter about what it expects from the
underling core Git. I'm sure the other Porcelain authors would also
like to be able to determine if they can rely on something, or not.
At the least we can just tell the user "Your Git old. Upgrade to new
Git today!". Yes, bad Engrish included... ;-)
> > Sure I can check the version, but until I know what version of Git
> > its shipping in I cannot put the check into git-gui.
> >
> > I was thinking about adding a "git-supported-features" plumbing
> > command that prints back feature code strings, much as our
> > network protocol supplies back the few feature codes it supports
> > ("multi-ack", "sideband", etc.).
>
> Problem is: it would be more interesting to have this program in _older_
> versions... ;-)
Lack of git-supported-features means only features before it coming
into existance? ;-)
--
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
