On Tue, Aug 16, 2011 at 03:37:33PM +0200, Michael J Gruber wrote: > > This isn't right. You are assuming that a remote called "foo" will have > > all of its branches in refs/remotes/foo. That's true under the default > > configuration, but technically speaking, the remote tracking branches of > > "foo" are defined by the right-hand side of foo's fetch refspecs. > > You are 100% right here, but... > > > So I think you want something more like this: > > ...the op still might want to filter simply by the remote name. That is a perfectly reasonable approach. It just should be called "--glob" or something, and not "remote". git-tag allows patterns to an explicit "tag -l", but "-l" is already taken for git-branch. > Reminds me that I have to resurrect my patterns-with-branches series.... Please do. I think it's a much simpler and more versatile solution to the same problem. -Peff -- 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