> Surely that's a github bug that you should be complaining to them about?
No, it's a known limitation:
https://help.github.com/articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository/
> I'm disinclined to split existing files because (a) it would complicate
> back-patching and (b) it would be completely destructive to git history.
> git claims to understand about file moves but it doesn't do a terribly
> good job with that history-wise (try git log or git blame on
> recently-moved files such as pgbench). And I've never heard even
> a claim that it understands splits.
>
> There might be reasons to override those disadvantages and do it
> anyway ... but this doesn't sound like a very good reason.
Ok, I will try to find workarounds for this, including forking.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
