Re: proper remote ref namespaces

2015-08-12 Thread Junio C Hamano
Marc Branchaud 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 c

Re: proper remote ref namespaces

2015-08-12 Thread Junio C Hamano
Jacob Keller writes: > Recently there was some discussion about git-notes and how we do not > fetch notes from remotes by default. The big problem with doing so is > because refs/remotes/* hierarchy is only setup for branches (heads), > so we don't have any clean location to put them. I wouldn't

Re: proper remote ref namespaces

2015-08-12 Thread Marc Branchaud
On 15-08-12 02:43 AM, Jacob Keller wrote: > Hello, > > Recently there was some discussion about git-notes and how we do not fetch > notes from remotes by default. The big problem with doing so is because > refs/remotes/* hierarchy is only setup for branches (heads), so we don't > have any clean lo

proper remote ref namespaces

2015-08-11 Thread Jacob Keller
Hello, Recently there was some discussion about git-notes and how we do not fetch notes from remotes by default. The big problem with doing so is because refs/remotes/* hierarchy is only setup for branches (heads), so we don't have any clean location to put them. Around the time of git 1.8.0, Joh