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

Re: [PATCH] sparse-checkout: improve OS ls compatibility

From
Derrick Stolee <stolee@gmail.com>
Date
Dec 19, 2019, 16:34 UTC
Message-ID
<c68de4d3-c5b6-fc70-a233-9702e9552d94@gmail.com>
In-Reply-To
<CAPyFy2AV2NG66LqBJr_Wb1_V5XhKnM+44m0H8FYa_3K4XupLow@mail.gmail.com>
On 12/19/2019 11:15 AM, Ed Maste wrote:
Show 16 quoted lines
> On Thu, 19 Dec 2019 at 08:56, Derrick Stolee <stolee@gmail.com> wrote:
>>
>> On 12/18/2019 9:45 PM, Eric Wong wrote:
>>> This goes on top of your patch:
>> ...
>>> +     ( cd "$1" && for i in *; do echo "$i"; done )
>>
>> Could we drop the "cd" and "echo" processes with this line instead?
>>
>>         for i in "$1"/*; do printf "$i\n"; done
> 
> That would output repo/a, but we could do something like:
> for i in "$1"/*; do echo "${i#$1/}"; done
> 
> echo's a builtin on any /bin/sh I'm aware of - do you have a /bin/sh
> with builtin printf but not echo?

I guess I am misremembering the benefits of printf over echo. Carry on with your approach.

Thanks, -Stolee

Previous: Ed MasteNext: Junio C Hamano
Message 8 of 24 in “sparse-checkout: improve OS ls compatibility”
  1. sparse-checkout: improve OS ls compatibilityEd Maste, Dec 19, 2019
  2. Derrick StoleeDec 19, 2019
  3. Ed MasteDec 19, 2019
  4. Derrick StoleeDec 19, 2019
  5. Eric WongDec 19, 2019
  6. Derrick StoleeDec 19, 2019
  7. Ed MasteDec 19, 2019
  8. Derrick StoleeDec 19, 2019
  9. Junio C HamanoDec 19, 2019
  10. Ed MasteDec 19, 2019
  11. Junio C HamanoDec 19, 2019
  12. sparse-checkout: improve OS ls compatibilityEd Maste, Dec 19, 2019
  13. Denton LiuDec 19, 2019
  14. sparse-checkout: improve OS ls compatibilityEd Maste, Dec 20, 2019
  15. Derrick StoleeDec 20, 2019
  16. Junio C HamanoDec 20, 2019
  17. Eric SunshineDec 20, 2019
  18. Ed MasteDec 20, 2019
  19. Junio C HamanoDec 20, 2019
  20. Eric SunshineDec 20, 2019
  21. Ed MasteDec 20, 2019
  22. Junio C HamanoDec 20, 2019
  23. Eric SunshineDec 20, 2019
  24. sparse-checkout: improve OS ls compatibilityEd Maste, Dec 20, 2019

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.