Re: Should we close python3-port branch in scons bitbucket?

Russel Winder <[email protected]> Thu, 14 Apr 2016 15:42:49 +0100

Newsgroups	gmane.comp.programming.tools.scons.devel
Message-ID	<[email protected]>

On Thu, 2016-04-14 at 10:14 -0400, Bill Deegan wrote:
> Russel (and all),
> 
> Since we'll be taking Russel's work in progress into main, it seems
> the
> presence of this branch is causing confusion.
> 
> Any reason not to close the branch?

I suspect, but have no experimental (or even theoretical) evidence – it
is just a hunch – that it might be hard to merge the python3-port
branch in my repository into mainline if the python3-port branch in the
mainline is closed.

If we are all agreed that now is a reasonably time to merge the Python
3 effort into the mainline default, I can merge my python3-port branch
into my default and close python3-port locally. This would allow the
python3-port branch in mainline to be closed with no consequences – as
far as I know.

The only threat to this course of action is if there is more effort on
mainline's default that needs merging before the grand python3-port
merge.

I am speaking from a position of relative Mercurial ignorance, so I may
be wrong…

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:[email protected]
41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev

signature.asc (application/pgp-signature, 819 B)