I agree. It's an inconvenience that we freedom lovers might be willing to accept, but when we interoperate with others who don't share our values, they will likely object and refuse to cooperate with us.
Some of them will cooperate and some will refuse. So what if some refuse? Exactly where do we need ALL of them to cooperate with us, so much that it would be a real problem if they do not? Still, that's no big deal for us. But if we want to be able to push patches we write without publishing a blob-ridden branch, we're going to have to make it easy for third parties who are not willing to tolerate any inconvenience for the sake of freedom. I am skeptical. I think we can live with that drawback, and our repository would still be a big step forward. Anyway. it is clear what you should do. Implement the conversion operation in whatever way is easiest, convert Torvalds' repository, publish our repository with the program and the correspondence table of revision hashes. They can add the feature to git if they want to. If you ask them to implement the feature in git, they will probably say they are not sure they care about it so why don't you implement it. So you may as well start by implementing it. -- Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org, www.gnu.org