Community
Participate
Working Groups
If a tree contains a subproject mode (160000), creating a commit in EGit can convert this to be a plain text file mode (100644), which results in Git assuming the target object is a blob in this project. If the target object is actually a commit in this project, we get weird failures from JGit trying to cast a RevBlob to a RevCommit, and `git fsck --full` gets confused, claiming a blob was used in a commit context. This results in a corrupt repository, because the target isn't valid anymore.
Could this be related to Bug 307560 ?
I think this is ok after 356664. Before this I could not commit a submodule change at all.
No objections. Closing.