Op 22-11-2011 19:04, Junio C Hamano schreef:
Vincent van Ravesteijn<vfr@xxxxxxx> writes:
Op 21-11-2011 18:37, Junio C Hamano schreef:
...
It is natural to expect "git branch --merged pu vr/\*" to list branches
that are contained in 'pu' whose names match the given pattern, but it
seems to try creating a branch called "vr/*" and fails, for example.
If this is what you naturally would expect, I would expect the
following "git branch vr/*" to work as well.
What would you say if we try to interpret the argument as a pattern
when the argument is not a valid ref name?
We don't, as that is inviting mistakes. "git branch vr/*" if you have a
vr/ directory in your working tree may create vr/a branch from where the
tip of vr/b points at by mistake.
The "--merged" option is an explicit clue that the user is not interested
in creating new branch, and the string being a pattern is additional clue.
The "--list" option was recently added for the explicit purpose of giving
such a clue as safety measure.
Well, that was the answer that I foresaw.
I will compose a patch implementing an at least consistent behaviour.
Vincent
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html