Re: [PATCH] branch.autosetupmerge: allow boolean values, or "all"
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 9, 2007, 02:27 UTC
- Message-ID
- <7vhcoexqeh.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <46919692.5020708@gnu.org>
Paolo Bonzini <bonzini@gnu.org> writes:
Show 7 quoted lines
> > Having prepared the patch below, I do not think if the original >> patch even wanted to have 'all' semantics. The surrounding text >> only talks about "off a remote branch" and I strongly suspect >> that nobody wanted to do this for a local branch case at all. > > If I remember correctly, the problem was that you are not sure that > remote branches are in refs/remotes.
Yes, the user can use traditional layout (e.g. refs/heads/origin is used as a remote tracking branch).
So the check with refs/remotes/ is not technically correct, but it should probably look-up the configuration to check the tracking, if we really want to be strict about it.
I personally do not care too much about it, though.