On 21 October 2016 at 20:32, Eric Blake <ebl...@redhat.com> wrote:

> On 10/21/2016 02:25 PM, Paul Eggert wrote:
> > On 10/21/2016 12:18 PM, Reuben Thomas wrote:
> >>         fsckobjects = true
> >> ​
> >> ​ I commented it out, and the checkout succeeded. If I then run "git
> >> fsck", I get lots of "error in tag foo: missingEmail" errors, and an
> >> error exit code. I guess this is just a minor annoyance?
> >
> > More like a major annoyance, I'm afraid. It means that the findutils
> > repository is slightly incompatible with Git and needs to be fixed on
> > Savannah. (If memory serves, this is due to a bug in older Git.) Fixing
> > a repository is not something one does lightly since it involves
> > changing history.
>
> Can we ascertain whether it is only unsigned tags that are affected (in
> which case deleting the broken tags and pushing corrected replacement
> tags with the same name in their place will solve the issue for all new
> clones, because commits remain unchanged), or are there also commits
> affected (in which case rewriting history will involve creating new
> commit ids for all descendants of the problematic commit, which is a
> rather dramatic effect, and which breaks any signed tags to old commit
> ids)?


T
​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.

-- 
http://rrt.sc3d.org

Reply via email to