tag:blogger.com,1999:blog-7028181408582795486.post4363715716546115171..comments2024-01-15T16:06:19.332+13:00Comments on Coding with the enemy: Common tasks with SubversionSeanhttp://www.blogger.com/profile/09419639577416328173noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-7028181408582795486.post-58246482663541779792008-08-08T11:07:00.000+12:002008-08-08T11:07:00.000+12:00I still learning Tortoise/Subversion, have had a f...I still learning Tortoise/Subversion, have had a few problems but have been able to resolve them. It would be good to see more posts about getting version control in place because not enough people take advantage of it.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-66615761428722314542008-08-08T01:58:00.000+12:002008-08-08T01:58:00.000+12:00@Andreas: But then other people cannot edit the sa...@Andreas: But then other people cannot edit the same file at the same time, right?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-55661567240948563912008-08-07T22:57:00.000+12:002008-08-07T22:57:00.000+12:00Lars. Thanks. I have updated my post to include ...Lars. Thanks. I have updated my post to include your quite important point.<BR/><BR/>Anon: If you are in a team, always update and run tests before you commit. I have explained further in the post.Seanhttps://www.blogger.com/profile/09419639577416328173noreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-11429255158927446882008-08-07T22:31:00.000+12:002008-08-07T22:31:00.000+12:00@B Jansen:This should be possible with the "svn:ne...@B Jansen:<BR/>This should be possible with the "svn:needs-lock" property. If it is set you must first use the "Get Lock" menu item in the explorer to change the file from readonly to writeable.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-32484931278755445992008-08-07T22:21:00.000+12:002008-08-07T22:21:00.000+12:00You can also just commit and do an update only if ...You can also just commit and do an update only if you get conflicts.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-20726875690506757112008-08-07T22:17:00.000+12:002008-08-07T22:17:00.000+12:00I'm a solo developer, still getting to grips with ...I'm a solo developer, still getting to grips with Subversion and TortoiseSVN. Some nice tips in there for a newbie, specifically the renaming/deleting thing.<BR/><BR/>Incidentally, I still do zips as well, but of course it's as easy as SVN using the GExperts "Backup Project" option... just a couple of clicks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-43745337520067126282008-08-07T22:03:00.000+12:002008-08-07T22:03:00.000+12:00I have been working with Perforce for a while, and...I have been working with Perforce for a while, and one feature I miss in SVN is that in Perforce all files are read-only untill you check them out of the repository. While checking them out, you imediately start an ew changelist. Does anyone know id this is possible in SVN as well?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7028181408582795486.post-40586034246996450172008-08-07T21:58:00.000+12:002008-08-07T21:58:00.000+12:00Good post! If you are in a team, and you are plan...Good post! If you are in a team, and you are planning a lengthy and complex change, you might want to consider branching so that you can commit to your work-in-progress branch without having to update. <BR/><BR/>This will allow you to commit as if you were working solo with the benefit of having version control throughout your lengthy changes.<BR/><BR/>When you are good and ready to put the code as complete, you merge the branch back into the trunk.Lars Fosdalhttps://www.blogger.com/profile/05635001623287214775noreply@blogger.com