Ok, not sure how to phrase this, first off, as you'll probably notice
in my post, I'm fairly new to subversion and tortoiseSVN altogether,
so forgive my ignorance. I'm not even sure what term to use to
describe my situation, so I'll explain it here.
I've been using TortoiseSVN along with Springloops for version control
for a little while successfully, until I recently encountered a
situation that I'm not sure the best method for dealing with it is.
Basically, I reached a point where I was developing some new
functionality, tested it locally, then committed the changes to SVN -
putting me at version number 49. Upon deploying that to my production
box, it took down the entire site (another story, no need to get into
it here). So I rolled back to 48 and site was fixed.
I found another solution for what I was trying to do and no longer
needed those files that were causing the issue. So I deleted them
through the TortoiseSVN->Delete menu and made some changes to some
other files, and committed them to SVN (which also looks like it
committed the deletes). Now at version 50, I deploy and again the
site goes down, so it looks like it's still uploading the files from
49. Again, I rollback to 48 and all is good and well.
Since then, I've made a few changes to other files, leaving me at
version 51 right now, but I still can't deploy it. So, my question is
obviously, how do I fix this? I do not want the files from 49 going
up to the server, but it seems like everything since then includes
them (even though I deleted them). I'm not familiar with Branching
and if that's what I should do or what, but if someone could provide
me, step by step (dummy it down), what I should do to get back on
track that would be a great help. Thanks in advance!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-09 07:27:45 CEST