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

Re: [PATCH 3/3] Teach "git branch" about --new-workdir

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 24, 2007, 12:42 UTC
Message-ID
<Pine.LNX.4.64.0707241337470.14781@racer.site>
In-Reply-To
<46A5DF1F.2030307@trolltech.com>
Hi,
On Tue, 24 Jul 2007, Marius Storm-Olsen wrote:
> The new-workdir feature doesn't *have* to be about symlinked .git/ 
> metainfo space, but could also be about symref'ed .git/ metainfo. (A 
> discussion was done in 2005s "Getting rid of symlinks in .git?", but the 
> conclusion was that it would slow it down too much? *ponder*)

Right. I would not do it as symrefs, but as a (potentially ugly, but small) change to have the git_dir set to the shared one, and only in case of config and HEAD resort to the new_worktree_git_dir.

This would probably be one variable in environment.c, exported in cache.h, set in config.c (which would say "new_worktree_git_dir = get_git_dir(); setup_new_git_dir(value);"), and the appropriate special handling in git_path() in path.c.

Show 5 quoted lines
> I think you're right in that this is probably not the appropriate itch 
> to scratch for a Windows developer to start with, and I have my own list 
> of issues to work on when I get the time. File stat'ing 
> (daemon/service), CRLF issues, de-SH'ifying commands, non-MinGW native 
> build of Git, etc.. Lots to keep my fingers busy :-)
;-)

BTW a friend reported a CRLF issue on Windows, _in spite_ of setting the gitattributes appropriately... Did you ever get something like that?

> Though, let me also say that I already love working with Git on Windows. 
> And I thank each and every one who's working on it, for providing such 
> an excellent tool.
Good to hear!

Ciao, Dscho

Previous: Jakub NarebskiNext: Marius Storm-Olsen
Message 30 of 46 in “Teach "git branch" about --new-workdir”
  1. 3/3 Teach "git branch" about --new-workdirJohannes Schindelin, Jul 22, 2007
  2. Daniel BarkalowJul 22, 2007
  3. Johannes SchindelinJul 22, 2007
  4. Julian PhillipsJul 22, 2007
  5. Johannes SchindelinJul 22, 2007
  6. Julian PhillipsJul 22, 2007
  7. Johannes SchindelinJul 22, 2007
  8. Julian PhillipsJul 22, 2007
  9. Jakub NarebskiJul 22, 2007
  10. Johannes SchindelinJul 22, 2007
  11. Johannes SchindelinJul 22, 2007
  12. Shawn O. PearceJul 23, 2007
  13. Junio C HamanoJul 23, 2007
  14. Shawn O. PearceJul 23, 2007
  15. Shawn O. PearceJul 23, 2007
  16. Johannes SchindelinJul 23, 2007
  17. Johannes SchindelinJul 23, 2007
  18. Marius Storm-OlsenJul 24, 2007
  19. Johannes SchindelinJul 24, 2007
  20. Junio C HamanoJul 24, 2007
  21. Johannes SchindelinJul 24, 2007
  22. Marius Storm-OlsenJul 24, 2007
  23. Julian PhillipsJul 24, 2007
  24. Marius Storm-OlsenJul 24, 2007
  25. Johannes SchindelinJul 24, 2007
  26. Josef WeidendorferJul 24, 2007
  27. Johannes SchindelinJul 24, 2007
  28. Josef WeidendorferJul 24, 2007
  29. Jakub NarebskiJul 25, 2007
  30. Johannes SchindelinJul 24, 2007
  31. Marius Storm-OlsenJul 24, 2007
  32. Marius Storm-OlsenJul 24, 2007
  33. Johannes SchindelinJul 24, 2007
  34. Marius Storm-OlsenJul 24, 2007
  35. Johannes SchindelinJul 24, 2007
  36. Marius Storm-OlsenJul 24, 2007
  37. Alex RiesenJul 24, 2007
  38. Marius Storm-OlsenJul 25, 2007
  39. Johannes SchindelinJul 25, 2007
  40. Steven GrimmJul 25, 2007
  41. Andy ParkinsJul 25, 2007
  42. Marius Storm-OlsenJul 25, 2007
  43. Johannes SchindelinJul 25, 2007
  44. Linus TorvaldsJul 25, 2007
  45. Christian MICHONJul 26, 2007
  46. Julian PhillipsJul 23, 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.