On Saturday 06 January 2007 2:57 am, Ariz Jacinto wrote: > if i may suggest, instead of learning another version control software, why > not learn the commands that will deal with the problem? afaik, most CVS
Yes, I'm trying to learn it. But in the meantme, my work is not versioned properly, because svn refuses to commit. So I need to use another system that works for me. > you can search for a script that automatically detects the "unmanaged" > or unversioned file/directory changes on your working copy which runs > "svn status" and then pipes the output to "svn rm" or "svn add" after Not an option (for me, at least). I'm too conservative to trust removing a bunch of files to a script. Maybe if it were just a test set of programs I'm using svn on, I can. > then again, you should use subversion when deleting , adding, etc. files > or directories on your working copy and not to make it guess. or you can > alias "rm" command to "svn delete" (mv to svn mv, cp to svn cp ) whenever > you're within the directories of your working copy (hint). Yes of course. I've seen the BIG warning itself. But this is exactly my problem. Changing one's habits is not that easy. Finger muscles have learned to act automatically as soon as the thought occurs in one's mind. So I know I will occasionally make the mistake esp. cp and mv (big NO NO under svn). My problem is that svn is not very forgiving about this mistake, and its error messages are quite opaque, and they don't give suggestions that are clear to me how to get out of the trap. Aliasing cp and mv might be the solution for me, until the bad habit goes away. Is it possible to do this aliasing (under bash) for versioned directories only? Greetings, Obet _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
