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

"Sparse checkout leaves no entry on working directory" all the time on Windows 7 on Git 1.8.5.2.msysgit.0

From
Kkonstunn@ngs.ru <konstunn@ngs.ru>
Date
Feb 6, 2014, 11:54 UTC
Message-ID
<web-57771132@mx45.intranet.ru>
Greetings.

I've tried to perform a single simple task to fetch data from the linux-next integration testing tree repo and sparse checkout the "drivers/staging/usbip/" directory.

I managed to perform it successfully under Linux with Git 1.7.1.

But I always failed to perform checkout under Windows 7 with Git 1.8.5.2.msysgit.0 facing the following error: "Sparse checkout leaves no entry on working directory".

Unfortunately, I haven't tried that under Linux with Git 1.8.5.2. So, don't know if there is the same problem.

However I typed the checkout directory in file .git/info/sparse-checkout by using different formats with and without the leading and the trailing slashes, with and without asterisk after trailing slash, having tried all the possible combinations, but, all the same, nevertheless, the error occured.

On Linux I stored the checkout directory in sparse-checkout file in the following way: "drivers/staging/usbip/". And everything was fine under Linux, but not under Windows.

However, I don't, of course, if the format of this directory really matters. May be the Git install on Windows 7 specific configuration is the reason?

Could you, please, tell me, what might be wrong? Am I doing something wrong or it's a bug?

Best Regards, Constantine Gorbunov

Next: Johannes Sixt
Message 1 of 4 in “"Sparse checkout leaves no entry on working directory" all the time on Windows 7 on Git 1.8.5.2.msysgit.0”
  1. konstunn@ngs.ruFeb 6, 2014
  2. Johannes SixtFeb 6, 2014
  3. Duy NguyenFeb 6, 2014
  4. Constantine GorbunovFeb 6, 2014

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.