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

Re: windows problems summary

From
CFChristopher Faylor <me@cgf.cx>
Date
Mar 2, 2006, 15:23 UTC
Message-ID
<20060302152329.GH2781@trixie.casa.cgf.cx>
In-Reply-To
<81b0412b0603020649u99a2035i3b8adde8ddce9410@mail.gmail.com>
On Thu, Mar 02, 2006 at 03:49:24PM +0100, Alex Riesen wrote:
Show 22 quoted lines
>This is just to summarize all the problems which make porting to that
>thing so boring. Maybe if we have them all on one page, it'd be easier
>to locate the workarounds (it can be one thread, for example).
>
>1. opened and mmaped files can't be removed or renamed
>  (caused workaround with reading index in memory)
>2. command can safely contain only one argument
>  (breaks and complicates passing things between processes)
>3. no fork
>  (slows down and complicates passing things between processes)
>4. non-unix permissions model
>  (breaks x-attr)
>5. real slow filesystems and caching
>  (makes everything slow. I noticed I'm trying to avoid git status!).
>  Caused workaround with manual checkout)
>6. real slow program startup
>  (makes everything slow, eventually may cause everything being put
>  in one super-executable, just to avoid spawning new processes,
>  with all associated problems. Makes scripting harder)
>
>I hope this message can be a start of a big porting thread,
>even though it is only about windows at the moment.
Are we *really* contemplating porting git to native Windows?
I guess I missed that memo.
cgf
Previous: Alex RiesenNext: Alex Riesen
Message 2 of 14 in “windows problems summary”
  1. Alex RiesenMar 2, 2006
  2. Christopher FaylorMar 2, 2006
  3. Alex RiesenMar 2, 2006
  4. Bertrand JacquinMar 2, 2006
  5. Alex RiesenMar 2, 2006
  6. Christopher FaylorMar 2, 2006
  7. Andreas EricssonMar 2, 2006
  8. Andreas EricssonMar 2, 2006
  9. Alex RiesenMar 2, 2006
  10. Shawn PearceMar 2, 2006
  11. Johannes SchindelinMar 2, 2006
  12. Alex RiesenMar 2, 2006
  13. Johannes SchindelinMar 2, 2006
  14. Eric W. BiedermanMar 31, 2006

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.