Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Re bug scraper If we migrate all bugs to GitHub, isn't there an issue # associated with github issues? If so, can we migrate the bugs such that the issue #'s stay the same? -Bill On Mon, Aug 28, 2017 at 2:02 PM, Dirk Bächle wrote: > Hi Russel, > > > On 28.08.2017 09:43,

Re: [Scons-dev] Problematic conflicts between C/C++ and D

so a better solution would be: env['SHOBJSUFFIX'] = env.get('SHOBJSUFFIX','.os') ? On Mon, Aug 28, 2017 at 2:17 AM, Russel Winder wrote: > On Wed, 2017-08-23 at 09:56 -0700, Bill Deegan wrote: > > Don't avoid TARGET.. > > > > Here's where it's defined: > >

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Hi Russel, On 28.08.2017 09:43, Russel Winder wrote: [...] The question then has to be how to bring the issues from Tigris to GitHub. GitHub issues has an API. If Tigris Issues also has an API then it is a question of writing a program, I guess in Python3, since that is likely easier than

Re: [Scons-dev] Problematic conflicts between C/C++ and D

On Wed, 2017-08-23 at 09:56 -0700, Bill Deegan wrote: > Don't avoid TARGET.. > > Here's where it's defined: > src/engine/SCons//Tool/cc.py:env['SHOBJSUFFIX'] = '.os' > src/engine/SCons//Tool/cxx.py:env['SHOBJSUFFIX'] = '.os' > > Will setting the SHOBJSUFFIX in the relevant D tools do the

[Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Whist I can't commit to working on anything in the next few weeks, I wanted to chip this in to the discussions. With bookmarks, remote head tracking and hgview working (at least on Debian Sid, not Fedora Rawhide), I have a renewed real like of Mercurial. It is better than Git for me. However