From: Segher B. <se...@ke...> - 2010-12-06 22:31:30
|
>>>> So we don't need a .gitattributes at all; at most we need to advise >>>> people to keep core.autocrlf off for our trees. >>> >>> Or, instead of hoping that everybody will read/do what we want them to >>> do with git (which is a big if - we don't have that amount of control), >>> we can enforce LF, >> >> Why would libusb do this, when no other project does? >> >> What is so special about libusb here? > > This is not in the absolute (and there's nothing special about libusb, > except the fact that we have 2 valid alternatives). Dunno what you mean here, "two alternatives"? > This is as opposed > to the alternative of not forcing people to find out that autocrlf will > only work to a certain extent, and that they must also apply safecrlf > under our conditions, vs enforcing -crlf on .sh/.ac/.am and leaving > people not having to care one bit about the line terminators for these > files, even if they use weird ____crlf settings. People will need exactly those same settings for any other open source project hosted in git, including a bunch that go out of their way to support MSVC as well. They're also the default settings for git, as far as I can see. Also, users who do not know this stuff are much more likely to use tarballs / zipfiles anyway, as has been pointed out to you a lot of times already. > We know how to ensure that people have the freedom to change their > ____crlf options if they so chose. Why then would we want to restrict > that freedom? Exactly similarly, we can limit all our source files to have lines of at most 40 chars, so they can be displayed on a C64; or get rid of all {}[] in C code since not every printer has those chars. According to you, this would be "not restricting freedom", and requiring a sane environment would be "restricting freedom". > But here we do have a known alternative, which is logically expected to > give our users more freedom (copy files between envs and have the > software still able to build), Copying files around like that does not work, has never worked, and will never work. It's why programs like "d2u" and "recode" exist. Segher |