Brian Gernhardt <benji@xxxxxxxxxxxxxxxxxx> writes:
> We had --heads for refs/heads and --tags for refs/tags, but no easy
> way to specify refs/remotes, which is going to be more common now that
> it's the default layout for clone.
Interesting.
I've never used --heads and --tags myself because
git show-branch heads/*
git show-branch tags/*
works perfectly well for me, and it often is not very useful to
look at _all_ the heads (tags are even much less interesting) in
a topic heavy repository anyway. IOW, I more often do something
like:
git show-branch --topics master heads/js/*
to see what Johannes has relative to "master".
I actually was thinking about removing these flags, not adding
--remotes, because
git show-branch remotes/origin/*
would work similarly and equally well.
Side note: in the above examples, I am taking advantage of the
fact that I typically do not have heads/ tags/ and remotes/origin
directory in the working tree and let shell pass the asterisk
unmolested to the command. Strictly speaking they should be
quoted from the shell.
Without --topics, git-show-branch treats all incoming refs
equally and shows the simmetric differences across them. When
you give --topics, the first ref is treated as "the base
version" and filters out the commits only on the first branch
from the output (that's why I gave --topics in the above example;
when I am trying to see what are still needed to be merged from
the js/* topic branches, I am not interested in the development
on 'master' since js/* topics forked).
-
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