## Reasons to adopt https://github.com/texmacs/texmacs There are many TeXmacs mirrors on github using git-svn.
I sugguest that we should use https://github.com/texmacs/texmacs There are several reasons: 1. I mirror it in a group named texmacs (I have invited vdhoeven to the group. And if accepted, I will transfer the ownership) 2. I'm running a cronjob for mirroring on my own server 3. I'm maintaining a svn commit user to github user mapping, see https://github.com/texmacs/texmacs/graphs/contributors ## Why I set up new TeXmacs repo on github? I forked Karl's texmacs repo on github last year, and begin to make it build using CMake. I made it and Karl improved it later. However, these changes haven't been merged into the official SVN repo. Why? Please see this PR: https://github.com/KarlHegbloom/texmacs/pull/12 There are too many changes to apply it on the SVN code bases. ## Work Flow and Pull Request The better work flow should be: 1. fork https://github.com/texmacs/texmacs 2. work on your branch based on the master (please **minimize** your changes and make it easier to merge) 3. create a PR on github 4. We will review the code and merge it into the SVN code base For Karl: You have made many improvements on TeXmacs. I suggest we should separate these changes into smaller PRs and merge it into SVN. You may fork https://github.com/texmacs/texmacs into github.com/KarlHegbloom/TeXmacs ---- On Sat, 07 Oct 2017 05:59:32 +0800 Karl Hegbloom <[email protected]> wrote ---- I'm fairly new with using git and github, and did not think of this sooner... Both Darcy Shen (@sadhen) and I (@KarlHegbloom) have put mirrors of the primary subversion repository---which is maintained by TeXmacs primary author, Joris van der Hoeven---up on github, to facilitate patch sharing, and to try and promote the use of git, perhaps. The problem is that instead of there being one initial git repository that was then cloned, we've each begun a separate repository, cloned via "git svn", maintained via "git svn rebase" on the svn trunk "vendor tracking" branch. And so when I add a git remote for sadhen-github and then fetch, it tells me that there are no common commits! Despite that, most of the file blobs are pretty much the same, I guess... It did not really download as much data as I was afraid it would. Despite that the git commit objects are not the same---they have different SHA1 because of something to do with how git svn works, I suppose---the file blobs are the same from one svn version to the next and so the git file blobs are also eq with identical SHA1 in both @sadhen and my github repository. I don't know that it really matters, since a git diff of my svn-trunk with @sadhen's master---the names of the branches that track svn with no other modifications---is an empty diff. So we can still work with this, I think. Another benefit of having them clone from the same base git repository is that then github keeps track of that, and links them more usefully, for the pull-request functionality, etc. If there is an official TeXmacs/texmacs.git available on github, then we can clone from that. I wonder if the svn repo can be configured to automatically cause a git svn rebase to happen, followed by a git push to send it up to github? Or that could be running as a daily or twice daily job on any computer that is always on... I wonder if github can automatically keep a svn to git mirror up to date? I think Launchpad can, but I'm not certain. blah blah blah blah... :-) -- [email protected] _______________________________________________ Texmacs-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________ Texmacs-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/texmacs-dev
