SVN epic fail

[wtfux]

What about this: Someone write a code change in "Submit Code" forum and when it's ready for svn, I can do the changes and upload it, if he/she can't do it himself/herself.

[PurpleYouko]

that sounds great. just what i had in mind.

[Drakia]

Well the reason to use SVN is so that we can keep track of who uploads what code (It is all logged to certain usernames). What the devs should do is create two seperate folders, one to keep the latest SVN in, and one to actually edit their code in. When they come up with something stable, update the SVN folder (SVN Update) then use something like WinMerge to compare the differences and copy their code over, this way they don't need to worry about overwriting someone elses code. Then they can commit those changes.

[wtfux]

Using Branches AND Trunk is a problem. See osRose svn: Trunk is way outdated.
I did not say that I'm the only one who uploads. You can still track the nicknames. I meant only PurpleYouko. Because Purple has problems using svn's.

[pepu]

we have to upload drop system i think

[Drakia]

Pepu, I just fixed the code you deleted You seem to have removed those two fixes you said you added, lol. Also, I think we should wait on the new drop system, or add it in a default-disabled state. At least until PY gives the go-ahead that it's stable enough to add to the SVN as default.

[lmame]

Boy, it's wild

[wtfux]

Purples drop system is already summited to the google svn. It seems to work right so far (tested some littl things). Dunno how far it is.

[pepu]

google svn link?

[wtfux]

viewtopic.php?f=40&t=1321