Re: [Libusb-devel] >=autoconf-2.63 no grokmultiline AC_CONFIG_FILES?

[Segher B. <se...@ke...>]

> I'm almost wondering if the situation is that we all have to have exactly
> the same settings, and that no one set is more forgiving than another?  If
> that's the case (and it may not be), that would put to rest the argument
> about making git-users do more up front, since it could go either way.

Everyone on unix systems has no problems.  There are a zillion different
kinds of mixed-up line ending things on mswindows; it certainly does not
help that with git, changing your autocrlf etc. settings does not make
your currently checked-out tree magically correct (you'll need to do a
clean checkout for anything to make sense again, or so it seems).

Ideally, the repo should work as-is for both unix and mswindows users if
they both use tools with sane defaults.  If we can get there, great!

> Is it necessarily bad to have CR's in the repository?

For text files?  Yes, absolutely.  For anything else?  Nope, git is 8-bit
clean.

> There are certainly
> some files that should be that way in the snapshot (and also some that
> should be LF-only in the snapshot).  In particular, for the snapshot, I'd
> like to see the MSVC stuff,

Yup, those files should be marked as binary -- we don't want to see diffs
of big auto-generated XML-like files anyway.

> source files, and documentation as CRLF,

Dunno about those.  It would be nice if other people could read them, and
if they were the same format as everything else.

> and the
> bash/autotools/make-specific stuff as LF.

I still don't understand why in your configuration those are checked
out as CRLF, but other text files are just LF (or, why don't do these
other files give similar problems?)

Maybe you should check out _all_ text files as LF?


Segher