RCharles Posted August 2, 2012 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 154 Reputation: 8 Joined: 05/31/12 Last Seen: May 15, 2014 Share Posted August 2, 2012 I've noticed that when you are really outdated with your svn and when you like to run a update, you are faced with bunch of errors upon compiling. So, is there a way for the late outdated svn to update without facing this errors? and should not also affect the src mods you've made. Quote Link to comment Share on other sites More sharing options...
Mystery Posted August 3, 2012 Group: Members Topic Count: 94 Topics Per Day: 0.02 Content Count: 2192 Reputation: 252 Joined: 11/11/11 Last Seen: June 24, 2020 Share Posted August 3, 2012 Not necessarily.. if your SVN working copy is outdated (severely), you will be faced with errors whenever you update to the latest just because codes where either moved around in the source, added where old codes where, etc. This goes for any single file in your SVN. Basically, you shouldnt keep your SVN working copy outdated for a while. I suggest you keep updated as much as you can especially if the SVN got overhauled (like the NPC folder recently). Whenever I can, I try to keep my working copy updated. Quote Link to comment Share on other sites More sharing options...
Question
RCharles
I've noticed that when you are really outdated with your svn and when you like to run a update, you are faced with bunch of errors upon compiling.
So, is there a way for the late outdated svn to update without facing this errors? and should not also affect the src mods you've made.
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.