topic added. I believe I added some customization to the pelican-bootstrap3 them and thus the creation of a repo to hold it. So unless I'm missing something, it should be retained.
-Bill On Thu, Nov 23, 2017 at 3:05 AM, anatoly techtonik <[email protected]> wrote: > Awesome. ) More proposals from my side. > > 1. SCons repos need `scons` label to compete in this list: > https://github.com/topics/scons > > 2. SCons website need to be moved to GitHub as well: > https://bitbucket.org/scons/scons-new-website > https://bitbucket.org/scons/scons-website > > This should probably be killed: > https://bitbucket.org/scons/scons-pelican-bootstrap3 > > On Wed, Nov 22, 2017 at 10:00 PM, Bill Deegan <[email protected]> > wrote: > > > > > > On Wed, Nov 22, 2017 at 9:46 AM, Bassem Girgis <[email protected]> > wrote: > >> > >> This is great news. I would recommend consolidating all the online > >> references to the new repo. Also what is the role of the bitbucket > repo? The > >> user contribution builders also need some sorting. I would be more than > glad > >> to help in any activity. > > > > > > Where are you seeing references to the bitbucket repo? > > Most likely they should all be changed. > > > > At this point the bitbucket repo is just historical. > > There are some outstanding pull requests which have yet to be migrated to > > github. > > > > -Bill > > > >> > >> > >> Best regards, > >> Bassem > >> > >> ---- > >> Bassem Girgis, PhD > >> Cell: +1(256)479-6124 > >> > >> On Nov 22, 2017 10:48 AM, "Eric Fahlgren" <[email protected]> > wrote: > >>> > >>> Special thanks to you, Bill, and all the others for reviving SCons and > >>> bringing it back to active life! It made my life so much easier being > able > >>> to continue using SCons as part of our migration to Python 3. I had > been > >>> right at the start of attempting to convert our build system over to > CMake > >>> when the stable 3.0 port came out, which saved me untold hours (or > days or > >>> weeks) of converting our build system, some parts of which are almost > 20 > >>> years old now. > >>> > >>> Eric > >>> > >>> On Wed, Nov 22, 2017 at 7:11 AM, Bill Deegan < > [email protected]> > >>> wrote: > >>>> > >>>> Special Thanks to Anatoly for tracking down the previous owner of > >>>> "SCons" and asking him to change thus freeing up SCons. > >>>> > >>>> Special Thanks to Steve Constable (formerly SCons on github) for > >>>> changing his github user id to free up SCons! > >>>> > >>>> You will have to update your remote settings under git. > >>>> > >>>> Assuming "upstream" was the remote name you're using to point at the > >>>> master SCons repo, the following command will update your git sandbox. > >>>> > >>>> git remote set-url upstream [email protected]:SCons/scons.git > >>>> > >>>> I'll be updating various bits of SCons wiki, buildbot, and website > today > >>>> to make sure they are all pointing at the proper (changed) URLs. > >>>> > >>>> -Bill Deegan > >>>> SCons Project Co-Manager > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Scons-dev mailing list > >>>> [email protected] > >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev > >>>> > >>> > >>> > >>> _______________________________________________ > >>> Scons-users mailing list > >>> [email protected] > >>> https://pairlist4.pair.net/mailman/listinfo/scons-users > >>> > >> > >> _______________________________________________ > >> Scons-users mailing list > >> [email protected] > >> https://pairlist4.pair.net/mailman/listinfo/scons-users > >> > > > > > > _______________________________________________ > > Scons-dev mailing list > > [email protected] > > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > > > > > -- > anatoly t. > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
