GExperts
Synced every now and then from git svn clone https://svn.code.sf.net/p/gexperts/code/trunk; Syncing steps: first time `git svn clone https://svn.code.sf.net/p/gexperts/code/trunk GExperts.git-svn`, then `git remote add origin https://github.com/jpluimers/GExperts.git` and `git push origin master`, then each additional time from inside the `GExperts.git-svn` directory: `git svn fetch` followed by `git svn rebase` and `git push origin`
- Quiet · last change 12-25-2018
- ★ 5 on GitHub
README
GExperts
Synced every now and then from git svn clone https://svn.code.sf.net/p/gexperts/code/trunk
Branches
masterthe latest sync from SVNdevelopthe latest merge of my work and the SVN; usually quite accurate, but might not buildfeaturesub-branches contain my changes, usually numbered (the number correspondes to the issue number it tries to address)
Note that the default branch is develop, which makes it easier for me to merge stuff.
Pull requests
If you like to cooperate on GExperts, but are not a fan of SVN, you can submit a pull request relative to the develop branch and I will try to forward it to Thomas Mueller, who maintains GExperts no SVN based SourceForge.
Sync instructions
For myself to know the steps for syncing this repository from SVN.
First time
git svn clone https://svn.code.sf.net/p/gexperts/code/trunk GExperts.git-svngit remote add origin https://github.com/jpluimers/GExperts.gitgit push origin master
Each additional time
From inside the GExperts.git-svn directory:
git checkout mastergit svn fetch- visually inspect the changes
git svn rebase- visually inspect the rebase
git push origin master

