News for hackers. Stuff that matters.
Re:Sunsetting Mercurial Support in Bitbucket by hiccuphippo on Tuesday August 20, 2019 @08:21AM (#20746056)
Is there any feature in mercurial that git doesn't have? Is there some plugin to allow mercurial users keep using the client with a git remote repository (like the one for using git with svn)?
Re:Sunsetting Mercurial Support in Bitbucket by durin42 on Tuesday August 20, 2019 @10:00AM (#20747113)
1) hg absorb

2) hg-git exists, and there's other things afoot that should be better

Re:Sunsetting Mercurial Support in Bitbucket by hiccuphippo on Tuesday August 20, 2019 @02:24PM (#20750250)
Just looked at hg absorb. It seems like a very useful feature but I understand it is an extension by Facebook. Can't someone make a similar extension for git?

...and I just found it: https://github.com/tummychow/git-absorb

Re:Sunsetting Mercurial Support in Bitbucket by Mindless2112 on Tuesday August 20, 2019 @12:06PM (#20748532)
As a daily hg-git user, could you elaborate on (2)?
Re:Sunsetting Mercurial Support in Bitbucket by 1wd on Tuesday August 20, 2019 @02:03PM (#20749960)
Re:Sunsetting Mercurial Support in Bitbucket by benibela on Wednesday August 21, 2019 @06:43AM (#20756065)
That would be helpful

I use hg-git to put all my Mercurial based projects on Github.

But the last OpenSUSE update installed Mercurial 5, but left the old hg-git for Mercurial 4. Now it does not work anymore.

Re:Sunsetting Mercurial Support in Bitbucket by 1wd on Wednesday August 21, 2019 @01:12PM (#20759162)
On Windows it is broken since TortoiseHG 4.5.2
Re:Sunsetting Mercurial Support in Bitbucket by benibela on Wednesday August 21, 2019 @06:24PM (#20762558)
TortoiseHG is really cool

I used to use it all the time on linux.

Unfortunately the OpenSUSE update also removed it. Completely, it is not even listed in the package management anymore.

No one wants to maintain non-mainstream software

Re:Sunsetting Mercurial Support in Bitbucket by andrewshadura on Tuesday August 20, 2019 @10:29AM (#20747378)
Changeset evolution for starters.
Re:Sunsetting Mercurial Support in Bitbucket by sterileopinions on Tuesday August 20, 2019 @11:23AM (#20747965)
You mean the thing that was only suitable for real world use by in-the-wild development teams last year? Something no repo provider really fully supports even to this day?

From HG's own documentation (https://www.mercurial-scm.org/wiki/ChangesetEvolution):

>While well on the way, the full implementation of the changeset evolution concept is still in progress.

HG's entire system requires far more investment in the tool than git will ever ask of you. And you probably don't need the feature in the first place. I consider changeset evolution a nifty feature, but it's also a devop smell in my book.

Re:Sunsetting Mercurial Support in Bitbucket by krupan on Tuesday August 20, 2019 @03:04PM (#20750717)
Changeset evolution has had the "beta" label for way too long. I started using it years ago and it was fine.

As far as smells go, its whole purpose is to make editing history less "smelly" than git's rebase -i followed by force push.

Re:Sunsetting Mercurial Support in Bitbucket by sterileopinions on Tuesday August 20, 2019 @04:17PM (#20751607)
> I started using it years ago and it was fine.

You are not a full blown development team, and beta software works for many people. That doesn't mean it's ready for prime time.

Re:Sunsetting Mercurial Support in Bitbucket by andrewshadura on Tuesday August 20, 2019 @01:21PM (#20749476)
No. Evolution was usable since 2015 at least. Supported by Bitbucket and others.

Evolution requires no effort whatsoever to maintain.

Re:Sunsetting Mercurial Support in Bitbucket by a_e_k on Tuesday August 20, 2019 @03:38PM (#20751082)
Revsets: a single, uniform syntax for querying and selecting commits. Used throughout Mercurial and accepted almost everywhere that a subcommand takes one or more commits as a parameter.

https://www.mercurial-scm.org/repo/hg/help/revsets