On 17 Jan., 12:59, "Pablo d'Angelo" <[email protected]> wrote:
> Then you can add your work to this repo and perform hg commit (or hgtk > commit, if you installed tortoisehg (which is quite nice...)). to > commit your changes to the local repo (same as with bzr). two changesets committed so far, but only locally > Then you can put that repo on the web. We can then easily merge your > changes into the master repo as sourceforge. > There seem to be lots of sites offering hg online repos (http:// > mercurial.selenic.com/wiki/MercurialHosting). I have two repos on > bitbucket.org, it easy to set up and use so far (but I haven't done > much work there yet). For now, I haven't put the repo online, but what I have done should be the next-best thing: I've made a mercurial patch reflecting the changesets needed to get the python_scripting branch up to my current development status quo. This patch is online at http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch4853.gz I made them from my two changesets 4852:bf77427fe623 and 4853:9de97bcfd3b2 by issuing the commands hg export 4852:bf77427fe623 4853:9de97bcfd3b2 > patch4853 gzip patch4853 I hope this is just what you need and convenient enough to use. Echoes welcome. Kay -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
