4 ms·
> Lots of reasons. I'd rather not go into an argument about it. It's not something that can be fixed: git is a no-go for us. I'm not interested in getting into
by JoshTriplett 11y ago
> Lots of reasons. I'd rather not go into an argument about it. It's not something that can be fixed: git is a no-go for us.
I'm not interested in getting into an argument, but I'm genuinely curious what reasons remain for people preferring mercurial. At the moment, apart from "got used to the UI", the main one I know of is more "native" Windows support (without needing a Cygwin-like environment to work in). I don't know if that's an issue for your project.
> I'd rather break free, not change masters.
Fair enough. In terms of repository hosting, moving to Savannah seems like the obvious choice there then. And assuming you have people available to do the work, you could always move to gnu.org or nongnu.org, depending on your tastes and the nature of the software your directory links to.
- kkmickos 11y agoCan't speak for anyone else but I use Mercurial because it's fast, user friendly and easy to extend with your own plugins.
- jordigh 11y ago> I'm genuinely curious what reasons remain for people preferring mercurial Top-level answers here: https://news.ycombinator.com/item?id=9467096 https://news.ycombinator.com/item?id=9467096 > moving to Savannah seems like the obvious choice there then. The only issue is that Savannah is static hosting. We have a bit of PHP that generates one page. We might be able to replace that with Jekyll, though.
- JoshTriplett 11y ago> The only issue is that Savannah is static hosting. We have a bit of PHP that generates one page. We might be able to replace that with Jekyll, though. Does it do so from dynamic server-side data, or could you run it on each new commit and serve the result as a static page?
- jordigh 11y agoYeah, we can probably do some sort of commit hook. It's not an impossible problem, just annoying.