search for: reinvest

...ded a very smooth transition path, where the conversion was merely a bump in the road, not a major mountain to climb over. In any case, I hope that we as a community don’t end up in a place where we are afraid of doing sweeping changes that make the codebase better. It is important to continually reinvest in the health of the codebase, and it isn’t bad to incentivize people to merge their changes upstream. Being overwhelmingly afraid of ‘breaking history’ is a path that leads stagnation and ultimate replacement by newer technologies. There are many other projects that have suffered this fate, usua...

...g about stuff that doesn’t matter. > > I agree that we should be able to make sweeping changes. I’m saying that I don’t think the direction I see us going in right now seems like it’ll work out well, and it seems easy to address my worries. > > >> It is important to continually reinvest in the health of the codebase, and it isn’t bad to incentivize people to merge their changes upstream. > > Agreed. However, as you know very well, merging upstream changes isn’t something that’s done over a weekend. First people have to know that a large change is coming and they probably sh...

hello, i am french student and i want configure a Asterisk server. when I want launch the server with the command safe_asterisk -vvvvvcf the server answer : Asterisk ended with exit status 1 Asterisk died with code 1 what is the signification of it please ? thank you lucas _________________________________________________________________ MSN Hotmail :

As a very frequent explorer of history, I really don't think this is as big an issue as it may seem. Even absent refactorings, you often run into the "wrong" commit when looking at blame (e.g., someone just added a comma rather than actually changing the code you care about), and have to look past that, to another previous commit. Any interactive blame tool ought to have an easy way