It still puzzles me how reason #3 is so common. How is it that changes get missed? Do you run "git status" when preparing commits and when preparing to push your changes? I'm wondering if there are simple things like customizing .gitignore or adding colors to the status output that could make #3 less common.
Sent from my iPhone On Jun 2, 2012, at 1:55 AM, Walter Bright <[email protected]> wrote: > > > On 6/1/2012 9:50 PM, Jonathan M Davis wrote: >> On Friday, June 01, 2012 21:45:13 Brad Roberts wrote: >>> Obvious fixes in: >>> https://github.com/D-Programming-Language/dmd/pull/978 >>> >>> What sort of testing passed for this commit? >> Given that _everything_ other than the dmd build itself failed, that would >> imply that either Walter didn't try and build anything other than dmd, let >> alone run any of the tests, or he didn't commit all of the changes that he >> made. >> > > Reason #3. > _______________________________________________ > dmd-internals mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/dmd-internals _______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
