We are not rewriting history to fix this so it doesn't really matter who is right or wrong. Mike
On Mar 9, 2015, at 9:13 AM, Ben Langfeld <ben@langfeld.co.uk> wrote:
I'm curious about this one... If git fsck complains about the issue, what is the justification for saying that Github is broken? How were these commits created with a format that git itself complains about?
On 9 March 2015 at 09:01, <cmrienzo@gmail.com <mailto:cmrienzo@gmail.com>> wrote: I switched to bitbucket.org <http://bitbucket.org/> just for the FreeSWITCH repo to work around this.
On Mar 8, 2015, at 20:34, Ken Rice <krice@freeswitch.org <mailto:krice@freeswitch.org>> wrote:
This is a known issue with github and will not be fixed
On 3/8/15, 3:39 PM, "Podrigal, Aron" <aronp@guaranteedplus.com <http://aronp@guaranteedplus.com/>> wrote:
Hi,
I'm trying to push the freeswitch git repo to my github, but I get the following error
remote: error: object 487128950df6ee433c131b5feaafe81ee86629f4:invalid format - expected 'committer' line remote: fatal: Error in object channel_by_id: 0: bad id: channel free Received window adjust for non-open channel 0. error: pack-objects died of signal 13
This is caused by having multiple authors on a commit (which in general is not allowed by git) and github verifies the commits and rejects it.
here is the output of git fsck
Checking object directories: 100% (256/256), done. error in commit 487128950df6ee433c131b5feaafe81ee86629f4: invalid format - expected 'committer' line error in commit 8574988c3a378b4d5861ecaeb0e958657635703b: invalid format - expected 'committer' line Checking objects: 100% (254227/254227), done.