1. Jurko Gospodnetić
  2. suds

Issues

Issue #28 resolved

Switch to Git(Hub)?

Bouke Haarsma
created an issue

Most FOSS development is going on in Git at GitHub. I've tried pushing to my own fork using a git-hg bridge, but that doesn't work smoothly. I really dislike Mercurial as a VCS and it's a barrier for me to get involved in providing pull requests.

Comments (7)

  1. Jurko Gospodnetić repo owner

    I haven't really considered it. Any reason I should other than personal preference?

    Personally I don't care if it is on Mercurial of Git, and I originally started it on BitBucket using Mercurial since there was already a mirror of the original suds project there, as well as a fork adding the initial Python 3 support.

    As far as I see:

    • both VCSs allow me the ability to commit and refactor my patches locally
    • both hosting sites allow me to have forked projects for easily staging my changes
    • both VCSs provide a command-line interface for easier scripting/automation
    • both make it blasted difficult to fix typos in ancient commit messages cry

    True, the names used for the underlying VCS operations differ, and so you have to adapt to a specific VCS's perculiarities, but logically they do seem to match 1-1.

    In my local workspace folder I have dozens of FOSS project checkouts - some done using git, some using Hg, and it seems to me that the 'reality' is that some people prefer one over the other and that there is nothing we can do to standardize it globally. I've found that my personal preference varies depending on which I've been using mostly last. smile

    Best regards, Jurko Gospodnetić

  2. Jurko Gospodnetić repo owner

    If it is really unbearable for you to use Hg, and that's the only reason for preferring the switch - feel free to create a git fork when needed, develop there and open issues here containing just a link to your git fork. Since I still like to review all the commits in detail - it does not really matter to me whether you provide them in a git or a Hg repo. smile

    Oh... and I think it goes without saying - thank you very much for any work you do put into the project. smile

    Best regards, Jurko Gospodnetić

  3. Bouke Haarsma reporter

    For me, Git is superior to Hg, mostly because Git allows rewriting history and makes it so much easier to recover from mistakes. I've tried working with Hg in the past, but I found it a major pain. Seeing how popular Git is, I think switching to Git will lower the barrier for people to contribute. Maybe it's just me and trying to force my Git-mindset upon Hg just won't work. Anyway thanks for the time you put into this project. :)

  4. Jurko Gospodnetić repo owner

    Well, excuse me for playing the devil's advocate here, but Hg does allow rewriting history as well. It just does not paint the same operation using the same colors - you can convert your commits into a patch queue, rearrange the patches, change their commit messages or their content, get them to look/feel whichever way you like and then recommit/finalize them... smile That routine is part of my regular work on suds. I have 3 or 4 unpublished branches at any time that I still have to find the time to clean up before pushing them back to BitBucket...

    As I said before - both git & Hg seem to allow the same operations and both have the same problem of rewriting ancient/pre-merge history. smile

    For me it may take me a few minutes to switch my hg/git mindset, but in the end - most of the time is spent in my design/code/research anyway. If I do get bogged down in some VCS detail, most often that's because there is something that peeked my interest there and not because 'I had to'. smile

    Best regards, Jurko Gospodnetić

  5. Bouke Haarsma reporter

    Thanks to Jurko for a Hg / MQ session, Hg is less of a mystery to me. However I still find git's branching/merging/rebasing way easier to understand. Hoping that this repo once gets upgraded to git, the solutions (either hack on github, or work with Hg) will work for me.

  6. Bouke Haarsma reporter

    Thanks to Jurko for a Hg / MQ session, Hg is less of a mystery to me. However I still find git's branching/merging/rebasing way easier to understand. Hoping that this repo once gets upgraded to git, the solutions (either hack on github, or work with Hg) will work for me.

  7. Log in to comment