git/rev-parse.c, branch v0.99

Add "--flags" and "--no-flags" arguments to git-rev-parse

2005-07-06T17:08:08Z

The scripts that use this (notably "git diff") will want to split up flags and file arguments.

git-rev-parse: support show sha1 names for pack entries

2005-07-04T04:01:11Z

This is actually subtly wrong. If a short match is found in the object directory, but would _also_ match another SHA1 ID in a pack (or it shows in one pack but not another), we'll never have done the pack lookup, and we think it's unique. I can't find it in myself to care. You really want to use enough of a SHA1 that there is never any ambiguity.

Make git-rev-parse support cogito-style "short hex names"

2005-07-04T03:27:06Z

Currently only for unpacked objects, but the infrastructure is there to do it for packed objects too.

Add "--all" flag to rev-parse that shows all refs

2005-07-03T20:07:52Z

And make git-rev-list just silently ignore non-commit refs if we're not asking for all objects.

git-rev-parse: add "--not" flag to mark subsequent heads negative

2005-06-26T18:34:30Z

If you have two lists of heads, and you want to see ones reachable from list $a but not from list $b, just do git-rev-list $(git-rev-parse $a --not $b) which is useful for both bisecting (where "b" would be the list of known good revisions, and "a" would be the latest found bad head) and for just seeing what the difference between two sets of heads are if you want to generate a pack-file for the difference.

git-rev-parse: re-organize and be more careful

2005-06-24T17:12:55Z

Output default revisions as their hex SHA1 names to be consistent. Add "--verify" flag that verifies that we output a single ref and not more (and disables ref arguments).

Change parent syntax to "xyz^" instead of "xyz.p"

2005-06-21T04:06:47Z

The ".pN" thing might be a common ending of a tag, and in contrast, ^ already is a special character for revisions so use that instead.

Make rev-parse understand "extended sha1" syntax

2005-06-21T03:28:09Z

You can say "HEAD.p" for the "parent of HEAD". It nests, so HEAD.p2.p means parent of second parent of HEAD (which obviously depends on HEAD being a merge).

git-rev-parse: flush "default" head when encountering something unexpected

2005-06-20T23:14:13Z

The unexpected thing is likely a pathname, we need the default for that too.

git-rev-parse: parse ".." before simple SHA1's

2005-06-20T15:29:13Z

This fixes "..*", since get_sha1() will happily ignore any garbage at the end and thus we never got to the ".." check before.