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

Re: re[4]: sparse checkout file with windows line endings doesn't work

From
Duy Nguyen <pclouds@gmail.com>
Date
Sep 20, 2013, 01:15 UTC
Message-ID
<CACsJy8BeT7ZP+ZQah7FR6ogqRNiiDZYP5SEs8J6J=+gEHU5MUg@mail.gmail.com>
In-Reply-To
<SDZYRFhOTCk2PDAuPVQvMjI4MjE1ODkw@IBMLT4>

On Fri, Sep 20, 2013 at 7:01 AM, Martin Gregory <marting@adelaideinterim.com.au> wrote:

Show 10 quoted lines
> Hi Duy ,
>
> re: [file created in gitbash]
>
>>>  Thanks. Please send me the file created by windows shell. I suspected
>>>  that windows shell may save it in some funny encoding like utf-16..
>
>
> Strangely, I had sent the file created by the windows shell ahead of the one
> created by gitbash, but here it is again :)

Sorry I must have missed it. Anyway there is a trailing space at the end of the rule. This is the content of your sparse checkout file in C syntax

"/CONFIGURATION\x20\r\n"

Maybe we could warn about trailing spaces.. Stripping them automatically is a possibility, but we need an escape hatch for (crazy?) people who actually have trailing spaces in there paths.

-- 
Duy
Next: Martin Gregory
Message 1 of 8 in “Re: re[4]: sparse checkout file with windows line endings doesn't work”
  1. Duy NguyenSep 20, 2013
  2. re[6]: sparse checkout file with windows line endings doesn't workMartin Gregory, Sep 20, 2013
  3. Duy NguyenSep 20, 2013
  4. Jeff KingSep 20, 2013
  5. re[2]: sparse checkout file with windows line endings doesn't workMartin Gregory, Sep 20, 2013
  6. Jeff KingSep 20, 2013
  7. re[2]: sparse checkout file with windows line endings doesn't workMartin Gregory, Sep 20, 2013
  8. Junio C HamanoSep 20, 2013

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.