git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: a few remaining issues...

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 10, 2007, 13:46 UTC
Message-ID
<Pine.LNX.4.63.0701101442520.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<81b0412b0701100440n6fe9e406yfe712cf236a784e2@mail.gmail.com>
Hi,
On Wed, 10 Jan 2007, Alex Riesen wrote:
Show 20 quoted lines
> On 1/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > 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.

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

Previous: Alex RiesenNext: Alex Riesen
Message 5 of 16 in “a few remaining issues...”
  1. Junio C HamanoJan 5, 2007
  2. Alex RiesenJan 5, 2007
  3. Johannes SchindelinJan 10, 2007
  4. Alex RiesenJan 10, 2007
  5. Johannes SchindelinJan 10, 2007
  6. Alex RiesenJan 10, 2007
  7. Johannes SchindelinJan 5, 2007
  8. Shawn O. PearceJan 5, 2007
  9. Johannes SchindelinJan 9, 2007
  10. Junio C HamanoJan 9, 2007
  11. Johannes SchindelinJan 9, 2007
  12. Shawn O. PearceJan 10, 2007
  13. Johannes SchindelinJan 10, 2007
  14. Juergen RuehleJan 5, 2007
  15. Junio C HamanoJan 8, 2007
  16. Junio C HamanoJan 8, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.