Thoughts on remotenames additions to remotebranches

Augie Fackler raf at durin42.com
Fri Jan 16 10:12:59 CST 2015


On Thu, Jan 15, 2015 at 05:42:58PM +0000, David Soria Parra wrote:
> Ryan McElroy <rm at fb.com> writes:
>
> > There are a few other small features that Durham thought would be useful as well:
> > * Allowing certain remote bookmarks to always be visible (eg, master/@/trunk remote bookmarks)
> > * Prevent local bookmarks from interfering with remote bookmark names (eg, prevent '/' in bookmark names)
> > * Use bundle2 to prevent race conditions with listkey after pushes
>
> I might a bit of an unpopular opinion here, but I prefer a unique prefix
> for remote bookmarks that can be forbidden (e.g. remote/mpm/@). This is

I like the unique prefix idea, but I'd propose paths/ so it lines up
with what you configure in hgrc.

http://green.bikeshed.org/

> less restrictive than forbidding '/'. In particular given that a lot
> of blog articles and general dvcs documentation use / as a delimiter
> for topic branches (including myself), e.g: dsp/cache. Having a unique
> prefix can be used to uniquly identify a remote bookmark if it has the
> same name as a local one.
>
>  1. I reate mpm/@ locally
>  2. I pull from mpm
>  3. I checkout mpm/@, mercurial warns me this is not unique but goes
>  for the local one first.
>  4. I can specify //mpm/@ to uniquly identify a remote bookmark or
>     /mpm/@ to uniquly idetnfiy the local one.
>
> - David
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel


More information about the Mercurial-devel mailing list