Since Gump(y) hasn't built for months, it can't complain more than it already is doing ;-).
The real question is whether we want to run Gump on the 5.0 branch as well as HEAD. ----- Original Message ----- From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, June 01, 2004 6:00 AM Subject: CVS branching Hi, So at some point soon (the next day or two), we want to put the current tomcat 5 code on a branch called tomcat_5_0 (the actual branch name is tentative but let's use tomcat_5_0 for example). We'll do this after tagging TOMCAT_5_0_26 on the main branch. The actual CVS command is easy: cvs rtag -r TOMCAT_5_0_26 -b TOMCAT_5_0 (repeat once for each tomcat CVS module, jakarta-tomcat-5, jakarta-tomcat-catalina, etc.) Subsequent checkouts and tagging operations against this have to specify -r TOMCAT_5_0 or else they work against the default, main/head branch. Commits are easy (don't need a branch specified) as they automatically work against the branch where the checkout was done. Is that it? Should we be concerned about the fact that the main/head codebase will not be as stable, so users trying to build head (or automated/nightly/gump trying to build head) may run into trouble? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
