Re: [Libusb-devel] CRLF in files checked out on Windows

[Pete B. <pb...@gm...>]

On 2010.12.07 12:44, Michael Plante wrote:
> Pete Batard wrote:
>>> On 2010.12.07 01:11, Segher Boessenkool wrote:
>>>> "text" for git means "do whatever line ending conversions you asked
>>>> for", etc.  It's the default on all files.  It does not mean "LF".
>>>
>>> [...] I still don't get how
>>> "text" does not equate "LF"
>
> I've seen both assumptions throughout this thread, which is why I pointed
> this out.  Segher's response is on the same page with me.

I'm considering text from the point of view of the repo, so maybe that's 
my mistake.

Our prime concern is what ends up in the repo, because all the rest 
derives from this. If a repo is always LF, then, as far as I know, it is 
not possible to use "text" ever and end up with LF files in it, hence, 
from the point of view of the repo, text equates LF, because the git 
executable on the end user platform will ensure that, no matter what 
conversion options are used, and no matter whether the file on the file 
system uses, the file ends up as LF in the repo.

I guess there are 2 aspects of text, one is input (how it affects files 
that are copied into the repo - and my understanding is that if you have 
text, you will end up with LF always, no matter your conversion options) 
and the other is output, which is the part where "text" can be 
interpreted as "do whatever line ending conversions you asked for"

So, equating text to LF depends at which end you stand.

When standing at the repository end (filesystem -> repo), can there 
exist any cases where "text" does not equate "LF"?

Regards,

/Pete