On 1/7/2013 10:03 AM, Leandro Lucarella wrote:
It's been pointed out several times, to avoid breaking the repository.
Yes, I do understand that.
What I don't understand is, having all the infrastructure already set up for you, why do you still want to use your own. Is an incredible duplication of work!
Well, if it breaks on Brad's build farm, I can't debug it. I need my own setup to debug it.
From what I see, using your own farm (which is clearly less polished than the auto tester because you are not testing clean checkouts, but you own working copy) is more work for everybody (including you) and more error prone.
Not so clear from my point of view. When I did the last release, working with two branches at the same time (staging and master), back and forth, I had a lot of mental confusion keeping track of which of my machines had which version of the code on it.
With doing dmd fixes as pull requests, I wind up with two git repositories for dmd. One is the 'master', which is linked to the main dmd github repository. Then, I have another git repository linked to my personal github account which I use to do forks and pull requests from.
I.e. I haven't figured out how to do pull requests from the repository linked to github d-p-l, and I haven't figured out how to push to github d-p-l from the walterbright fork, if it is even possible. It makes my brain hurt even thinking about it.
_______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
