On Wed, 2008-06-04 at 19:12 -0400, Steve Huston wrote: > Hi folks, > > I created a git repository for qpid porting efforts. The svn trunk as > of ~30 minutes ago is the master in git. I suggest that we create a > branch for each port, unless Manuel wants to rebase his Solaris port > on the refactoring I did for Windows. Of course, I'd rather have it go > that way, but we could also just each do a git branch and go and then > synch them up later.
I'd agree with the branch for each port as it will still be possible to create a merging branch from that as well, but if we base one port on the other then it will no longer be possible. Also Manuel's code besides the small things to make it compile under Solaris is very much in the same vain is the current code whereas Steve's patch is much bigger. If I had to guess I'd say that (once we've resolved the dynamic_cast problem one way or another) it would be simple to merge the Solaris port without a major fuss, but the Windows port is much more intrusive so will demand more thinking/scrutiny. > > For discussions on issues that arise, let's keep things here on this > list rather than on the git-based wiki stuff. Ok? > > The git repo is at git://github.com/shuston/qpid-port.git > > After we get some concensus on whether or not to start from the > Windows refactor, I'll add the Windows stuff in. I'd create a branch for the windows port anyway - we can always merge things later when we decide to. Incidentally in case it isn't clear yet, one of the major benefits of git is that it has extremely good support for tracking merges between branches, so it makes more sense to start with separate branches then merge them. Andrew
