So there is no need to check whether there is a trailing garbage when we encounter an error. And we cannot use this way, for example: ref: refs/heads/feature \n If we find the first '\n' index. In this example, index will be equal to "referent->len". And we totally ignore this case. > > + ret = fsck_report_ref(o, report, > > + FSCK_MSG_TRAILING_REF_CONTENT, > > + "trailing garbage in ref"); > > + } > > + > > + /* > > + * Missing target should not be treated as any error worthy event and > > + * not even warn. It is a common case that a symbolic ref points to a > > + * ref that does not exist yet. If the target ref does not exist, just > > + * skip the check for the file type. > > + */ > > I think the common terminology for this is 'dangling symref'. Perhaps we > could shorten this to simply say: > > Dangling symrefs are common and so we don't report them. > Thanks, I will improve this in the next version.
