Hi all! First of all, thank you all for your assistance! The code is in the SF repo all right, I made sure by going through a complete pull-up-clone- branch-compile cycle, and it's looking just fine.
Phew... this was a major piece of work - kept me busy for a good two weeks, every day all day. Of course a good part of the time went into learning the tools - first I had to decide which tools to use, then I hadn't used SWIG before, and I also had to read up a great deal about Python/C++ integration to make it all come out nicely. I hope to see some use of this branch and a discussion of how the new possibilities can be turned into a benefit for the users and developers alike. Of course it's all still very rough-and-ready, there may be bits missing or failing here and there, but I hope the big picture is all right. On 20 Jan., 00:38, Pablo d'Angelo <[email protected]> wrote: > From http://mercurial.selenic.com/wiki/Export, it seems that hg bundle > is the preferred way for contributing changesets. I have tried to import > your changes into the sourceforge repository using hg import, I hope it > worked fine. Pablo, thank you for taking time off your busy schedule with cpfind to help me get my code in! I think you may have misunderstood the mercurial documentation. It says in there that 'hg bundle' is to export merge changesets, but there weren't any merges in mine, it was just composed of two successive changesets, applied to the branch as created by you, each only with one parent. In this case I take it the export command is the one to use, as I gleaned from the export tutorial http://mercurial.selenic.com/wiki/TutorialExport Anyway, it worked - and since I don't expect to throw such patches at you guys all too often and the effort to put them in doesn't seem to be excessive, I hope this is an acceptable method for you for now. I'm considering setting up a repo with bitbucket, as you recommended, but I'm not there yet. 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
