[Scons-dev] Trial SCons migration to git on github

[Bill Deegan]

Dirk,

Here's an example workflow from buildbot..
http://trac.buildbot.net/wiki/SubmittingPatches
See "How to create a patch".


git clone git at github.com:myusername/buildbot.git
cd buildbot
git checkout -b myfixes origin/master
git add $files_that_matter
git commit

<run tests here>

git push origin myfixes

Pretty much the same for every git open source project
Note how simple it is. Allows working multiple branches with out bookmarks
and multiple heads. The branches go away on pull request merge.
So not much work to change the wiki page.. can probable even just copy
theirs..

When we first chose mercurial, I wasn't aware that branches persisted
across pull requests causing a mess in the master repo.
Eventually hg added bookmarks (which initially IIRC didn't persist push
requests so sharing in multiple sandboxes (multiple platforms) was a pain).

I'm just tired of the pain. I think that's a reasonable reason to switch.

-Bill


On Sun, Jan 10, 2016 at 6:22 AM, Jason Kenny <dragon512 at live.com> wrote:

> If this is about using git. I see two options with the least amount of
> work.
>
>
>
> 1)      User uses a git-hg plug-in to checkout with git.
>
> or
>
> 2)      Move the code in SCons to git in bitbucket. I don’t think we have
> a reason to do a major move to another site, when the current one works
> great with git as well.
>
>
>
> Jason
>
>
>
>
>
>
> *From: *Russel Winder <russel at winder.org.uk>
> *Sent: *Sunday, January 10, 2016 7:49 AM
> *To: *dl9obn at darc.de; SCons developer list <scons-dev at scons.org>
> *Subject: *Re: [Scons-dev] Trial SCons migration to git on github
>
>
>
> On Sat, 2016-01-09 at 14:09 +0100, Dirk Bächle wrote:
> >
> […]
> > I would also like to make us a clear statement first, about what we
> > want to change/migrate and why we want to do it. I'm currently
> > trying to find examples of large open-source projects (not some small
> > repos, maintained by a single person) that have moved from
> > Mercurial to git. Can anyone give pointers?
> > My goal here is to analyze the log/commit history in order to find
> > out whether the migration actually did have a measurable effect
> > on things like "frequency of commits per month", "LOC touched per
> > month", "new committers per month" and so on.
>
> Probably the most high profile Mercurial → Git switch has been the Go
> project.
>
> The core of their rationale was workflow for pull request review and
> acceptance. I suspect also that Google is trying to switch all their
> work to Git.
>
> Go switched from a Google hosted Mercurial repository with Rietveld as
> the review system, to a Google hosted Git repository mirrored on GitHub
> with Gerrit as the review system.
>
> --
> Russel.
>
> =============================================================================
> Dr Russel Winder      t: +44 20 7585 2200   voip:
> sip:russel.winder at ekiga.net
> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20160110/6ac2a875/attachment.html>