Re: proper remote ref namespaces

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 12, 2015, 19:35 UTC
Message-ID: <xmqq1tf8l2p8.fsf@gitster.dls.corp.google.com>
In-Reply-To: <55CB63C5.8090708@xiplink.com>

Marc Branchaud <marcnarc@xiplink.com> writes:

> Not a lot.  Existing DWIMery already handles ambiguous branches, by
> preferring a local branch name over any remote ones.  The only teaching
> that's really needed is ...

You need to remember that there are five useful things you can do to mutable things.

 - Creation can be covered by teaching "clone" to put a new-style
   refspec but the same change needs to also go to "remote add".

 - Reading is done by the DWIMery in ref_rev_parse_rules[] (your
   point above).

 - Updating is automatic, as "fetch" does not have any funny
   built-in intuit and blindly follows configured fetch refspec.

 - Deletion by "branch -d -r" and "remote remove" needs to be
   careful about designing how the case where both old and new
   hierarchies exist should be handled (my gut feeling is "delete
   both", but there may be funny corner cases).

 - Enumeration by "branch -l -r" probably shares the same issue as
   deletion.