Re: [Scons-dev] Hg vs Git

Hmm. I've used (in order, more or less), PLS (which I expect nobody to know), Clearcase, RCS, CVS, Arch, TLA, HG, BZR, and Git. I won't claim to have used svn in any real sense. The first 4 of that list were centralized version control systems and so not applicable to this discussion. Of

Re: [Scons-dev] Hg vs Git

It would certainly make it easier for me to contribute; not that I've had that much to contribute recently, but git is in my fingers now and I have to remind myself how to do things in hg. On Mon, May 9, 2016 at 1:13 PM, Bill Deegan wrote: > All, > > So it sounds like

Re: [Scons-dev] scanning before emitting

FYI, I have used the protoc tool myself in the past. If you get it working well, I would like to see this tool make it into the regular distribution. I'm not sure the process has a strict guideline atm, but the idea would be to add it to the new contrib repo

Re: [Scons-dev] scanning before emitting

Very welcome. For future reference, this issue should really have gone to the users-list instead :) V/R, William On Mon, May 9, 2016 at 8:58 PM, Schleimer, Ben via Scons-dev < scons-dev@scons.org> wrote: > > Also, if you are talking about getting implicit dependencies and > cross-language

Re: [Scons-dev] scanning before emitting

> Also, if you are talking about getting implicit dependencies and > cross-language dependencies, then you need version 2.5.0+ Ah, thank you. I missed that in the release notes. I'm running with 2.4.1 right now. I'll checkout 2.5 then... > >The emitter should only return the outputs of the

Re: [Scons-dev] Hg vs Git

Hi there, On 09.05.2016 16:57, Rob Boehne wrote: For me, scons is the ONLY project I work on that uses Mercurial, and having to translate each and every command is a real pain. I¹ve also NOT contributed back many changes I¹ve made to get Python to build properly on old UNIX systems, primarily

Re: [Scons-dev] scanning before emitting

Also, if you are talking about getting implicit dependencies and cross-language dependencies, then you need version 2.5.0+ V/R, William On Mon, May 9, 2016 at 7:47 PM, William Blevins wrote: > The emitter should only return the outputs of the protoc call, so java, > cpp,

Re: [Scons-dev] scanning before emitting

The emitter should only return the outputs of the protoc call, so java, cpp, or python files, correct? The emitter isn't supposed to output (for example) the java class files; thus, I don't know why you would run the scanner at all. V/R. William On Mon, May 9, 2016 at 7:25 PM, Schleimer, Ben via

Re: [Scons-dev] Hg vs Git

On Mon, 2016-05-09 at 10:13 -0700, Bill Deegan wrote: > All, > > So it sounds like (from limited consensus), that switching to Git > now, > would remove a significant barrier to contributing code/fixes? > We just need to be careful that Git supporters are quick and vocal, whereas Mercurial folk

Re: [Scons-dev] Hg vs Git

All, So it sounds like (from limited consensus), that switching to Git now, would remove a significant barrier to contributing code/fixes? -Bill On Mon, May 9, 2016 at 8:12 AM, Tim Jenness wrote: > > > On May 9, 2016, at 07:57 , Rob Boehne wrote: > > >

Re: [Scons-dev] python3-port branch in scons/scons repo has been updated with Russel Winder's python3-port branch

On Mon, 2016-05-09 at 07:53 -0700, Bill Deegan wrote: > Russel, > > The SCons__Python3 is your repo, correct? > I don't see such in bitbucket. Didn't you pull/merge from: https://bitbucket.org/russel/scons__python3 This is the repository I was writing of. -- Russel.

Re: [Scons-dev] Should we close python3-port branch in scons bitbucket?

On Mon, 2016-05-09 at 07:49 -0700, Bill Deegan wrote: > Russel, > > The work is currently on python3-port in the  scons repository, and > not yet > on default. > (though buildbot may indicate it, that is incorrect.. look at the hg > logs > in the steps.) > > I think I'd like to get 2.7 passing

Re: [Scons-dev] Hg vs Git

> On May 9, 2016, at 07:57 , Rob Boehne wrote: > > For me, scons is the ONLY project I work on that uses Mercurial, and > having to translate each and every command is a real pain. > I¹ve also NOT contributed back many changes I¹ve made to get Python to > build properly on

Re: [Scons-dev] Hg vs Git

For me, scons is the ONLY project I work on that uses Mercurial, and having to translate each and every command is a real pain. I¹ve also NOT contributed back many changes I¹ve made to get Python to build properly on old UNIX systems, primarily because it was using Hg. I doubt I¹m alone in this,

Re: [Scons-dev] Hg vs Git

Russel, I would say inertia postponed a decision. I'd like to change to git, but it's not a high priority. I'd like to get py2/3 work done and released and then revisit. -Bill On Mon, May 9, 2016 at 5:42 AM, Russel Winder wrote: > There was a flurry of activity about

Re: [Scons-dev] python3-port branch in scons/scons repo has been updated with Russel Winder's python3-port branch

Russel, The SCons__Python3 is your repo, correct? I don't see such in bitbucket. -Bill On Mon, May 9, 2016 at 5:27 AM, Russel Winder wrote: > On Sun, 2016-05-08 at 10:38 -0700, Bill Deegan wrote: > > See subject. > > > > Next up. I'll be setting up a python3 buildbot

[Scons-dev] Hg vs Git

There was a flurry of activity about potentially switching from Mercurial to Git at the beginning of the year. The topic seems to have died down. Can I assume that this means Mercurial won the debate and that we will not be switching from Mercurial to Git – even though BitBucket is now a Git

Re: [Scons-dev] Should we close python3-port branch in scons bitbucket?

On Sun, 2016-05-08 at 10:18 -0700, Bill Deegan wrote: > Russel, > > I've pulled from your python3-port branch into a scons owned repo and > updated. > Running tests, then I'll push back to scons/scons repo. > > Should I then merge down to scons/scons ? Sorry to be late answering this, but it

Re: [Scons-dev] Should we close python3-port branch in scons bitbucket?

On Tue, 2016-05-03 at 13:31 -0400, Bill Deegan wrote: > Russel, > > Can't you do a pull request from your python3-port branch to scons' > python3-port branch? No I can't as far as I know, but this is now an issue that history has passed by :-) -- Russel.