"q66" <quake...@gmail.com> wrote in message news:ejygjkiyboebpginj...@dfeed.kimsufi.thecybershadow.net... > On Saturday, 4 February 2012 at 21:14:28 UTC, Nick Sabalausky wrote: >> "Walter Bright" <newshou...@digitalmars.com> wrote in message >> news:jgk65f$c0b$1...@digitalmars.com... >>> >>> .C (that's capital C; obviously that never worked on Windows) >> >> That *can* work. Windows filenames may be case-insensitive, but they're >> certainly not caseless. Not from Win95 onward anyway. (Obviously I'm not >> saying .C is a good way to go.) >> >>> >>> For me, I find worrying about it about as productive as arguing whether >>> tabs should be set to 4 or 8. >> >> Ok, so then why not just make the leap? Nobody *wants* .c (including you, >> apperently), and many people would find it to work better with .cpp. If >> you're so indifferent about it, then why keep clinging to .c? > > There is at least one serious issue with moving - it would break *all* dmd > pull requests. That does not mean I agree with the .c extension, however. > :)
I thought Git was supposed to be able to intelligently handle moved/renamed files? So shouldn't fixing those pull requests amount to "pull, possibly fix merge conflicts, push" just like with any other upstream change?
