Re: [Scons-dev] Multiple heads in repository

Anatoly, I'm not sure which part of "I made a mistake. I fixed it" you mis-understood. The multiple heads was caused by having an unfinished commit in one sandbox. committing in a second, then committing in the first. It's been resolved. -Bill On Mon, Dec 7, 2015 at 4:28 AM, anatoly techtonik

Re: [Scons-dev] Code of conduct?

On Fri, Dec 4, 2015 at 7:10 PM, Bill Deegan wrote: > All, > > Perhaps it's a good idea to add an official code of conduct for SCons. > http://blog.codinghorror.com/the-hugging-will-continue-until-morale-improves/ > > The following site seems to provide a reasonable

Re: [Scons-dev] SCons running on pypy?

On Wed, Nov 25, 2015 at 7:01 PM, Bill Deegan wrote: > There is an existing framework "timings" though right now the data reporting > is a bit broken. > http://buildbot.scons.org/timings > > The records have subversion versions and mercurial SHA's as the index and > are

Re: [Scons-dev] Multiple heads in repository

Is it a problem with Mercurial or with Bitbucket? I mean could we avoid that if we switch to Git or GitHub? On Wed, Nov 25, 2015 at 7:04 PM, Bill Deegan wrote: > I made a mistake. > Then I fixed it. > I had two sandboxes, and one had previous releases changes in it but

Re: [Scons-dev] Tests for SCons.Debug

I see. The problem is that in professional reviews that I used to, the phrase "Test?" from reviewer without any other context means that the change needs a test that is missing. I also think that the conflict could be resolved earlier if you let me know that you do not think that this change

Re: [Scons-dev] Code of conduct?

On Mon, Dec 7, 2015 at 7:58 PM, Dirk Bächle wrote: > Hi all, > > On 04.12.2015 18:10, Bill Deegan wrote: > >> All, >> >> Perhaps it's a good idea to add an official code of conduct for SCons. >> >> http://blog.codinghorror.com/the-hugging-will-continue-until-morale-improves/ >>

Re: [Scons-dev] Code of conduct?

An extra 2cents of opinion from me.. ;) A few things a CoC would help with: 1) It could encourage more participation on the mailing lists. Open source projects have been notorious for scathing responses to simple questions. Surprisingly I've been at clients who have used SCons for years and never

Re: [Scons-dev] Code of conduct?

Hi all, On 04.12.2015 18:10, Bill Deegan wrote: All, Perhaps it's a good idea to add an official code of conduct for SCons. http://blog.codinghorror.com/the-hugging-will-continue-until-morale-improves/ The following site seems to provide a reasonable code. http://contributor-covenant.org/

Re: [Scons-dev] Code of conduct?

On 07.12.2015 21:35, Alexandre Feblot wrote: Hi, Call me the Grinch, but I have the feeling there are 2 kinds of people in the world: * those who behave naturally, who don't need such written CoC because it is obvious for them, * those who would need it but definitely won't read and consider