bookmarks: validate changes on push (issue6193) (BC)

[Pulkit Goyal]

Hi,

Right now I know 3 big companies which uses bookmark but not the
default behavior.  We definitely want to improve current bookmark
behavior and make BC changes (if required) so that default bookmark
behavior is good to use.

I mean to kick-start that discussion from sometime and also go through
your proposal. However I will be a bit slow here since I am on
vacation for next two weeks. Sorry about that! I will get back to this
after that.

Regards
Pulkit

On Thu, Oct 24, 2019 at 4:00 PM Augie Fackler <raf at durin42.com> wrote:
>
> (+Pulkit explicitly)
>
> > On Oct 23, 2019, at 10:00, Sandu Turcan <aturcan at gmail.com> wrote:
> >
> > I'd like to revisit how bookmarks are validated on push. They aren't
> > currently, and I think it would make sense to have the same checks as
> > we do for a local bookmark change.
> > There is a proposed implementation here: https://phab.mercurial-scm.org/D6776.
> > It enforces the same rules, and can be overridden by --force.
> > _______________________________________________
> > Mercurial-devel mailing list
> > Mercurial-devel at mercurial-scm.org
> > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
>