Re: Automatically-generated regexp documentation

[Eric Blake]

On 10/21/2016 02:39 PM, Reuben Thomas wrote:

> ​hey seem only to be tags: git fsck --verbose says only for each error:
> 
> Checking tag 68c0e85dba93471b4f7d450ae2e6139a56574549
> error in tag 68c0e85dba93471b4f7d450ae2e6139a56574549: missingEmail:
> invalid author/committer line - missing email
> ​
> I can't see any errors for commits.

I count 97 such broken tags; and I verified I can push replacement tags
(tag 68c0e85 was for FINDUTILS_4_3_5-1; if you do a fresh clone, tag
68c0e85 is now gone, and replaced by an identically-named annotated tag
6ee72b929 with my email as tagger).  I'm planning to script the
conversion of all the tags, but am trying to figure out if it is worth
back-dating the tags, and whether an unsigned annotated tag or a simpler
lightweight tag is the better thing to push in place of each tag that
gets corrected.

At any rate, I'll post the commands I used to make the conversion, once
it is complete; here's my starting point.

$ git fsck 2>&1 | sed -n 's/error in tag \([^:]*\).*/\1/p' > broken

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature