using git / svn and dealing with version no

[squidsk]

Originally Posted by ub.ch

can you give more detail? Because for me it does not work

You need to setup two git repositories, though in theory it should work with 2 branches in the same repository. One repository/branch is solely for committing changes to vBulletin (i.e. upgrades) the other repository/branch is where your customizations are committed. When you apply an upgrade to the first repository/branch you then fetch it to the second and apply a git rebase to have your customization applied to the new "base" code.

I finished the article and have submitted it for approval with staff.

--------------- Added [DATE]1453494919[/DATE] at [TIME]1453494919[/TIME] ---------------

If you wanted to continue using svn you could do a similar thing where the vbulletin commits are on the trunk line and your changes are on a branch. Every time you commit a new vbulletin version to the trunk do an svn merge to your branch to upgrade you customizations to the new versions of svn.