Re: a few remaining issues...

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jan 10, 2007, 12:40 UTC
Message-ID: <81b0412b0701100440n6fe9e406yfe712cf236a784e2@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.63.0701101320300.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On 1/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 16 quoted lines

> > On 1/5/07, Junio C Hamano <junkio@cox.net> wrote:
> > > This is not meant to be an exhaustive list, and I probably will
> > > change my mind after I sleep on them, but before I go to bed,
> > > here are a handful of glitches I think are worth fixing.
> >
> > Maybe we should at least mention another cygwin quirk:
> > cygwin (or is it its bash?) treats .exe files and +x-files without
> > extension somehow stupid: it prefers the file without extension
> > to the .exe. For example, after installation of git-merge-recursive
> > you have the old python script and git-merge-recursive.exe in
> > the same directory. Guess which one is used... Right, the old
> > python script. Same for count-objects and other recently
> > rewritten scripts.
>
> I just sent out a patch in my mail "[PATCH] Makefile: add
> clean-obsolete-scripts target" which should help.

Well, you also have to give people at least notice _when_ the target should be called. It can take long time until the victim notices that he has git-branch (from .sh) and git-branch(.exe). And that in two places: in the installation target directory and in the build directory (because in windows it is not fcking possible to remove "." from the beginning of PATH).

> But in general, it should be fine to be called just once.

Don't think so. We still have candidates for conversion into C (git-checkout and git-commit being my favorites).