DMD build

[Marco Nembrini]

On 29.12.2012 12:18, Daniel Murphy wrote:
> "Andrei Alexandrescu"<SeeWebsiteForEmail at erdani.org>  wrote in message
> news:kbl3eh$2qe8$1 at digitalmars.com...
>> On 12/28/12 4:39 PM, Brad Roberts wrote:
>>> What impact does this have on the open pull requests?  If it's going to
>>> suddenly break every one of them, then I think it's a particularly bad
>>> idea.
>>
>> There are dozens of open pull requests and if worse comes to worst people
>> will agree to fix their requests because the request for changing
>> extensions has enjoyed considerable popularity.
>>
>>> The benefit is debatable and the cost is pretty annoying.
>>
>> The benefit is we'll avoid resurrecting a debate that comes back and
>> again. Technically there's no reason to move with the change, but right
>> now we're wasting time and burning through karma. Making the change shows
>> respect for the community and for working together in an environment that
>> has few gratuitous idiosyncrasies.
>>
>> Let's do it.
>>
>>
>> Thanks,
>>
>> Andrei
>
> You want to screw up over a hundred open pull requests and destroy the
> commit history... for what?  Because every year or so someone complains
> about the file extensions?  Anyone that takes longer than 5 minutes to work
> out what's going on probably shouldn't be trying to change the compiler's
> build process.
>
> Put a note in the readme, the makefile, and/or the wiki page on building the
> compiler, and leave the source alone.
>
> Daniel.
>
>

Nobody answered the important question: does it "break" pull requests?

In my (limited) understanding git supports renames and pulls will be 
"broken" in the same way the are when there's a new commit on the 
original repo: people will just have to rebase their changes on it. I 
did some googling and found nobody complaining about this problem, so I 
assume there's some way to avoid it.