The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#1
|
|||
|
|||
using git / svn and dealing with version no
Heya!
we are (still) using svn to manage our vbulletin instance. So far so good and all works well, but the main pain in the a•• is the upgrading process! SVN marks _all_ new files as conflicted, just because they have a different version number PHP Code:
We are planning on moving to git; but as far as I can see, the problem is still the same. I just don't want to go through all files and clear the conflicts. NB: some "core" files have been modified by us, I do know which ones, but the whole point of a versioning system is to know have to deal with those Or am I doing the update process wrong then you or what is best practice? Best |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|