Hi,

On Tue, 23 Jan 2007, Andy Parkins wrote:

quoted text
> On Tuesday 2007 January 23 15:20, Johannes Schindelin wrote:
> 
> > MinGW and cygwin differ in one very important point: cygwin needs an extra
> > dll, MinGW does not.
> >
> > However, the development environment is still console-based, with a bash
> > so you can run configure and simple bash scripts. It is definitely more
> > catering to Unix types than Windows types.
> >
> > So yes, there is a bash, and there is a less, and there is perl.
> 
> Those are just tools for MinGW though aren't they?  They aren't needed to run 
> the final executable object?  MinGW just spits out a native windows .exe - 
> i.e. plain windows.

Yes. But it _does_ have a dependency on perl and bash. For example, when 
you merge git-merge-one-file is spawned -- a bash script.

quoted text
> There is no reason to suppose that joe-random-developer will have bash, 
> less and perl, even if they do have git.  Which was kind of the point I 
> was making - there is no pager to rely on in Windows, so why not just 
> drop it.  Okay, so MinGW comes with some nice UNIXy tools, but MinGW is 
> the compiler, not the environment.

You reminded me that I was not precise enough: MSYS provides the UNIXy 
tools, and the compiler, MinGW is just the headers and import libraries.

And while we already depend on bash and friends -- which we put into 
GIT_EXEC_PATH -- we can ship more: "less".

quoted text
> Am I still misunderstanding?  I'm looking out for the time when
> 
> C:\SomePath> git commit -a
> 
> will work (I know - it's a long way off yet).

You need an editor, that is for sure, but it is not _that_ far off. Thanks 
to Johannes Sixt, committing works already (if you don't encounter the 
same problem starting vi as I do).

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html