[Scons-dev] Hummm…
Tim Jenness
tjenness at lsst.org
Sat Jun 11 11:43:16 EDT 2016
I agree. I don’t want to upset the apple cart and I’m definitely not trying to force a switch through. The github import was trivial so I’m more than happy to delete and reimport as scons default evolves. Of course, I have no idea if hg can import patch sets exported from git with format-patch.
—
Tim Jenness
> On Jun 11, 2016, at 03:25 , Dirk Baechle <tshortik at gmx.de> wrote:
>
> Hi there,
>
> I don't like being under pressure, so what's basically wrong with keeping everything "as is" and pulling Tim's changes directly into our hg repo? One might argue that this would impede the progress somewhat by making it harder for Tim to merge changes back from "default ". But that's more his problem...at least it doesn't make me leap into action immediately.
>
> Best regards,
>
> Dirk
>
> Am 11. Juni 2016 08:27:57 MESZ, schrieb Russel Winder <russel at winder.org.uk <mailto:russel at winder.org.uk>>:
> It just struck me that Tim Jenness has (subtly :-) switched the current
> active Python 3 work from Mercurial on BitBucket to Git on GitHub. We
> thus are under pressure to:
>
> a. all get stuck in using Git on GitHub as a temporary measure so as to
> get the evolving PR merged into the Mercurial on BitBucket mainline
> asap and hence avoid a rift.
>
> b. switch to Git on BitBucket and transfer Tim's stuff back to
> BitBucket.
>
> c. switch to Git on GitHub.
>
> Clearly c is perhaps overly revolutionary, especially at such short
> notice. b might be revolutionary and will annoy a lot of people but it
> will please a lot of people, the question is which group is in the
> majority. a is the path of least resistance (and as we know resistance
> if futile), and so may be the thing for people to do.
>
> I have taken a clone of Tim's Git repository and am playing with it,
> not quite as I type, but very shortly afterwards.
>
>
> --
> Sent from my Android with K-9 Mail._______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org <mailto:Scons-dev at scons.org>
> https://pairlist2.pair.net/mailman/listinfo/scons-dev <https://pairlist2.pair.net/mailman/listinfo/scons-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20160611/d20136f5/attachment-0001.html>
More information about the Scons-dev
mailing list