{"thread":{"id":"9055","subject":"Some questions about git-name-rev","startedAt":"2007-07-16T08:20:25Z","lastAt":"2007-07-16T08:20:25Z","messageCount":1,"participants":["David Kastrup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"47522","messageId":"86abtwyd2u.fsf@lola.quinscape.zz","threadId":"9055","inReplyTo":null,"subject":"Some questions about git-name-rev","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-07-16T08:20:25Z","receivedAt":"2007-07-16T08:20:25Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\nHi, I am working on git support in Emacs.  This involves putting\nversion labels into the mode line and using them for specifying\nrevisions to diff.\n\n40 digit commit numbers are not really fun for that.\n\nSo I need to use git-name-rev.  If I call it with the option --tags,\nit might return an empty string.\n\nIf I don't call it with --tags, _and_ the commit number I feed into it\nis the output of some git-rev-list, am I _guaranteed_ to become some\noutput?\n\nNow is there a way to _abbreviate_ the output to the shortest _valid_\nform, namely not have something like ref/remote/heads/branchname (or\nsimilar) when branchname is sufficient?\n\n-- \nDavid Kastrup\n"}]}