Subversion clients can now write to GitHub
github.com
github.com
I'm genuinely curious: what use case justifies this? Correct and clean merges and history are a major selling point of Git. Is this for people on Git-using projects who can't be bothered to learn a new VCS?
Also, you still have correct and clean merges, but since it's somewhat difficult for me to figure out what your last base version was when an svn client commits, it uses the latest version number of any submitted file as one parent and the current head as the other for anything that needs to merge, so the history may have more parents in it than are strictly necessary. If the merge does not happen cleanly, the server will reject the merge and you have to update and fix locally, like normal SVN. However, since the concept is new, I wanted to leave as much information in the Git history as possible, thus the extra parentage information.
What does the Git DAG end up looking like when a commit comes in from a mixed-rev WC? Do you have any examples I can see?
http://gitx.frim.nl/seeit.html
There is also an interesting fork which I have yet to try:
Not quite the same, I know, but the best thing if you want to use a combination of hg and github.