František Kučera <konfere...@frantovo.cz> writes: > Dne 18. 11. 19 v 13:01 Malcolm Matalka napsal(a): >> I have no idea how to evaluate if your flow is a good idea or not. > There >> is nothing conclusion I've found on the internet or talking to >> people. > > I understand that this might be better described, because the > documentation <https://www.mercurial-scm.org/wiki/Bookmarks>, > <https://www.mercurial-scm.org/wiki/NamedBranches> talks rather about > how particular features work – than giving an advice when use which one. > >> If I'm the CTO of an engineering team of 100 devs banging away at a > >> monorepo, are named branches too heavy for them for shortlived > > changes? Should they use bookmarks? Topics? Am I setting myself up > for > spending a ton of person-power in a year trying to get a sluggish > repo > to work? > > And with Git you can run into a situation that something weird happened > in the past, but you have no clue why or who did it and you are unable > to recover the original state and reproduce the scenario because certain > pieces of information are missing. I experienced several awkward > situations and wasted time with Git… This is one of reasons why I love > Mercurial – it is much better in history recording and it is much harder > to loose the information with Hg than with Git (especially the tags and > branches).
I agree those are powerful features of hg, but also, I make branches probably 100x more often than I have to deal with funky situations like that. It's like we have this amazing new motor that beats anything on the market but nobody can figure out how to open the car door. There is also "safety in numbers" when it comes to git. Meanwhile, us in the hg world can't even agree on the best way to make a branch. If not being prescriptive on how to use hg is an explicit decision of the community, that's ok. At the same time, we need to accept that many people don't value some of those great features of hg and just want to know how to make a branch and merge it, and if we aren't going to give them that answer then we should expect them to go where they can find it and we should not expect explaining revsets to them to be compelling. > > Franta > > _______________________________________________ > Mercurial mailing list > Mercurial@mercurial-scm.org > https://www.mercurial-scm.org/mailman/listinfo/mercurial
signature.asc
Description: PGP signature
_______________________________________________ Mercurial mailing list Mercurial@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial
