You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mkdir treebank
cd treebank
git svn init http://sweaglesw.org/svn/treebank --stdlayout --prefix=svn/
for tag in `git branch -r | grep "tags/" | sed 's/ tags\///'`; do git branch $tag refs/remotes/$tag; done
git svn fetch
The SVN repository (http://sweaglesw.org/svn/treebank/) didn’t contain branches, so I have created branches for the two tags I found: foo and packard-2015. Note that these tags do not look very interesting and maybe they could be removed in the SVN repository. That would make the process even simpler, tracking only the trunk branch.
With the repository ready, I created the GitHub repository and pushed to it
We don’t have automation yet. If Woodley updates its SVN, all I need to do is:
git svn fetch
git push --all -u origin
The first command retrieves the news from SVN to my local machine. The second command pushes the news to GitHub. Eventually, a new tag or branch can be created by Woodley, in that case, I may also need to create git branches for them before pushing to GitHub.
Since the FFTB is not updated very often, I feel the manual solution can work for now, but I wonder if I have any way to me informed by SVN changes. Does anyone know any alternative to subscribe to SVN changes?
The text was updated successfully, but these errors were encountered:
This repo was created with the commands below, following the step-by-step from http://www.sailmaker.co.uk/blog/2013/05/05/migrating-from-svn-to-git-preserving-branches-and-tags-3 that is consistent with the git-svn documentation.
The SVN repository (http://sweaglesw.org/svn/treebank/) didn’t contain branches, so I have created branches for the two tags I found:
foo
andpackard-2015
. Note that these tags do not look very interesting and maybe they could be removed in the SVN repository. That would make the process even simpler, tracking only the trunk branch.With the repository ready, I created the GitHub repository and pushed to it
We don’t have automation yet. If Woodley updates its SVN, all I need to do is:
The first command retrieves the news from SVN to my local machine. The second command pushes the news to GitHub. Eventually, a new tag or branch can be created by Woodley, in that case, I may also need to create git branches for them before pushing to GitHub.
Since the FFTB is not updated very often, I feel the manual solution can work for now, but I wonder if I have any way to me informed by SVN changes. Does anyone know any alternative to subscribe to SVN changes?
The text was updated successfully, but these errors were encountered: