btw, it goes without saying that if we adopt the verbose-numbered-tagging scheme i just described, then right before one starts the commit/merge procedure, one would have to do a 'cvs log' to see what the next tag-sequence-number would be. and since cvs lacks atomicity across multiple command-line invocations, one should complete the procedure as quickly as possible to avoid another developer stepping in and causing a problem in the middle. (again, somebody probably knows how to do this alot better than i do, so i'm looking forward to learning something). other option is 'human-powered' transactions with explicit personalized 'start' and 'end' tags for 'locking' (like start-mike-1, end-mike-1) ... which i feel is overkill for us.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831495#3831495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831495 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
