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
Doing so only works with trunk, of course. In fact, git-svn would operate on svn.example.org/repo/trunk only; tagging would still happen in native svn.
For git svn dcommit to work, every commit in the history of the synced git branch needs to have a svn-id annotation.
Most tutorials on the net are about retaining git history in svn, whereas wp-release explicitly wants to omit history.
https://wiki.bnl.gov/dayabay/index.php?title=Synchronizing_Repositories#Lossy_history_with_git_merge_.2B_git_svn_dcommit suggests to (squash-)merge master into the git-svn remote branch and just committing the merge commit:
Doing so only works with
trunk, of course. In fact, git-svn would operate on svn.example.org/repo/trunk only; tagging would still happen in native svn.For
git svn dcommitto work, every commit in the history of the synced git branch needs to have asvn-idannotation.http://stackoverflow.com/questions/160608/how-to-do-a-git-export-like-svn-export#7397656 suggests a simple
rsync.