News for hackers. Stuff that matters.
Re:Heptapod – Mercurial for Gitlab by BeetleB on Thursday August 27, 2020 @12:30PM (#24295332)
That's what I meant by outdated documentation.

I personally use bookmarks. They're simple to use. However, people have issues using them in a team setting (by default it doesn't sync the bookmarks when there's a push, I think). I have not explored topics - looking at Heptapod it seems they prefer topics, so it may be the way to go.

If you're the only developer, then bookmarks should do everything you want.

Re:Heptapod – Mercurial for Gitlab by Already__Taken on Thursday August 27, 2020 @03:20PM (#24297544)
I'm reserving judgement on HG but the comments saying it just works and is so easy gives me a good chuckle were I've had to set up all sorts that's non-obvious. topics not branches? cool ok. command not found, right uh enable extension 'topics =' yep sure obvious ok, Huh wired error now. oh pip install hg-evolve has topics in it fine ok.

go add a remote to an existing repo. lovely ux there.

and now you're telling me about bookmarks, I've a docs page open to read about phases, that seems kinda neat. at first glance thought it seems like a solved problem of protected branches and separate forks.

Re:Heptapod – Mercurial for Gitlab by BeetleB on Thursday August 27, 2020 @04:09PM (#24298072)
As I said - the only people who complain are those who are git users :-)

People who've not used git and come to mercurial don't find anything wanting in it.