Hi, On Tue, 29 May 2007, Shawn O. Pearce wrote: > 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... ;-) When in doubt, you can always test the return value to check if the command line option is accepted... Ciao, Dscho - 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
