smf added a comment.

  In https://phab.mercurial-scm.org/D4312#77596, @idlsoft wrote:
  
  > @smf I just noticed your name on 
https://www.mercurial-scm.org/wiki/BookmarkUpdatePlan, which puts your comments 
into a larger context.
  >  This would definitely be an improvement, and reduce the scope of what this 
extension does.
  
  
  I think that page has a typo: it should be "discussed at the London sprint." 
Ryan and I were quite eager to change this behavior of not moving bookmarks. It 
was one of the experiments I mentioned in my previous comment. Over the next 
year or so, I learned there was a big difference between Ryan's use-case (the 
monorepo) and the everyday repo (average repo on Bitbucket): having one (and 
only one) centrally controlled repo is easy to set a policy like "don't move 
bookmarks."
  
  In the wild, there are tons of unknown variables of how people are currently 
relying on the behavior; in particular, scripts. In fact, I have a few scripts 
that do rely on this behavior. Changing that at this point (by default, without 
a flag) is ill-advised in my opinion.
  
  > Would you consider also addressing the `hg bookmark NAME` doing two very 
different things depending on the bookmark already existing?
  
  At this point, I would prefer not to change default behavior for similar 
reasons as above.

REPOSITORY
  rHG Mercurial

REVISION DETAIL
  https://phab.mercurial-scm.org/D4312

To: idlsoft, #hg-reviewers, pulkit, marcink
Cc: mharbison72, smf, markand, marcink, durin42, jwatt, pulkit, mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to