Show 21 quoted lines
> "Mikael Magnusson" <mikachu@gmail.com> writes:
>
>> 2008/6/25 Jeff King <peff@peff.net>:
>>> On Wed, Jun 25, 2008 at 12:08:15PM -0400, Jeff King wrote:
>>>
>>>> Since you seem to be testing for-each-ref, maybe it would make sense to
>>>> put together a test script that exercises each of the atoms?
>>>
>>> Hmm. Actually, there is a test in t6300 that runs with each atom name.
>>> Unfortunately, it doesn't bother actually checking the output for
>>> sanity, so the fact that these atoms returned the empty string was
>>> missed.
>>
>> The documentation also says "tree" and "parent" should work (which they
>> also don't).
>
> The doc does not say any such thing. A tag object does not have 'parent'
> nor 'tree' header fields.
>
> Neither a commit have 'object' nor 'type' header fields and you cannot ask
> for them when showing a commit object.
Ah, sorry, I read this paragraph:
In addition to the above, for commit and tag objects,
the header field
names (tree, parent, object, type, and tag) can be used
to specify the
value in the header field.But not this one (which perhaps should be right after the
above instead of 3 paragraphs down):
In any case, a field name that refers to a field
inapplicable to the
object referred by the ref does not cause an error. It
returns an empty
string instead.