Hi, On Wed, 10 Jan 2007, Alex Riesen wrote: > On 1/10/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > > On 1/5/07, Junio C Hamano <junkio@xxxxxxx> 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. Okay. Fair enough. So maybe this is the wrong approach: maybe the "all" target should look for _all_ executables if there is a script of the same name, and in that case remove it; and the "install" target should do the same in the gitexecdir? > > 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). I was referring to make clean-obsolete-scripts; make; make clean-obsolete-scripts being necessary, because the script somehow got a newer time stamp than the executable. But yes, I think there are way more candidates, my pet peeves being git-ls-remote and git-fetch. 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