Opened 4 years ago

Closed 4 years ago

#3274 closed defect (invalid)

GitHub repository contents looks broken

Reported by: alexander.alekhin Owned by:
Priority: major Milestone: undecided
Version: master Keywords: github, git, repo


Fresh cloned repository from GitHub? contains fsck warnings.

$ git clone .
$ git fsck
Checking object directories: 100% (256/256), done.
warning in tree e1576c8594a1ed95914ef5ac0f1d70edaa440ae2: contains zero-padded file modes
warning in tree acd1ee822f4cb73ea9d59d82c04feec0612e9b07: contains zero-padded file modes
warning in tree 6a32700b6d727db34a238cb9f34fd575ff0a3277: contains zero-padded file modes
warning in tree 4d02d2de063f0432fbe876764f6de9cd9ab60d19: contains zero-padded file modes
Checking objects: 100% (87897/87897), done.
$ git --version
git version 2.1.0

Any thoughts how to resolve this?

Change History (2)

comment:1 Changed 4 years ago by sa2ajj

It looks like this problem can't be resolve without rewriting the whole history.

So my inclination is just to live with it.

comment:2 Changed 4 years ago by alexander.alekhin

  • Resolution set to invalid
  • Status changed from new to closed

Thanks for reply!

I dig this problem, looks like these commits are very old ("git show" shows files from v0.7+), so I agree that history rewriting is not acceptable.

Note: See TracTickets for help on using tickets.