Michael Haggerty <mhag...@alum.mit.edu> writes:
> Add cross-references between the manpages for git-for-each-ref(1) and
> Signed-off-by: Michael Haggerty <mhag...@alum.mit.edu>
> There is a lot of overlap between the functionality of these two
Two differences I most often use (i.e. take advantage of) are:
- The former is about showing 0 or more matching refs, and not
matching anything is a perfectly normal condition, i.e.
$ git for-each-ref refs/heads/no-such
exits with status 0. The latter can be used with --verify to
check if one ref exists, on the other hand.
- The former takes the match-from-left-to-right pattern (similar to
the usual pathspec match), while the latter matches from the
$ git for-each-ref refs/heads/* ;# only one-level names
$ git for-each-ref refs/heads/** ;# catches both master and mh/path-max
$ git show-ref master ;# refs/heads/master, refs/remotes/origin/master,...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html