What's the objective? To provide the person doing the build a list of files that have changed in the current build relative to production? What actions will that drive? It sounds like a solid branching strategy will resolve the issue of managing production updates.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Jackson Sent: Monday, June 27, 2005 8:00 AM To: info-cvs@gnu.org Subject: Getting tag information without checkout I'm trying to find out what files a tag owns and then inturn find out what tags a specific file belongs to. The problem is that I need to do this without checking out the file every time. I am trying to set up a notification system for ant builds for some code that is moving from a development environment to production environment. The person preforming the move is not a developer so the build itself needs to warn them that the file has been modified by multiple tags recently and there could be a conflict with a version on the production machine. Any ideas welcomed, Yolan ************************************************* * Yolan (Aaron Jackson) [EMAIL PROTECTED] * * http://mlug.missouri.edu/~yolan/ * * AIM: YolanLINUX, YolanOTHER, YolanLAPTOP * * ICQ: 74624109 * ************************************************* * Doubling Technologies * ************************** _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
