Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Ok your starting to make a little sense now. One thing that I want to clarify is when you say bug you mean bug fix as in this revision of the file fixes this bug, right? And your saying that the bug maybe fixed on multiple branches of the same file and tags can't express that, right? Ok sounds like a feature that is a start in the right direction but still needs some work. The fact that you can't apply a bug id after a commit is done is a bit of a draw back. The fact that you can't apply more than 1 bug id to a revision is a anther drawback I can easily envision 2 bug fixes relying on the same file/revision. The fact that you apparently can't remove a bug id is also a problem. The fact that the same bug id can be on several revisions of the trunk/same branch doesn't make much sense. It still doesn't work for my senario, i.e. I want to create a Change Set that defines a fix or feature that a build manager can use to create a new build. If a bug id is on multiple revisions of the same file how does the tool (or the build manager) know what version to take. It still sounds like I want to use tags which brings me back to the point about applying a tag at commit. Am I missing something here. Thanks Matt S. "Tony Hoyle" <tmh at nodomain.org> wrote in message news:cu15s7$u99$1 at paris.nodomain.org... > Matt Schuckmann wrote: > > Ok I had to upgrade the client and the server to version 2.0.62.1869 and > > now: cvs commit -B test_bug works. > > > > However, cvs up -B test_bug does not check out the revision of the file with > > the test_bug bug ID assigned. > > In fact it doesn't seem to do anything at all. > > It sets a boundary for branch merges. Using it on its own won't > actually do anything. It's used to extract the set of revisions that > are affected by that bug for each file so they can be merged into > another branch. > > If you just want a list of files which the bug is in, something like: > > cvs -q log -B test_bug -S -R > > Will do the trick. > > This will be a lot easier once the GUI support gets up to speed (this > usually lags little as the GUI writers understandably wait for a feature > to be fully stable before supporting it). > > > Is it possible to apply a Bug ID after a file has been commited? > > Not at the moment. > > > Is it possilbe to apply more than one Bug ID to revision? > > Bug IDs apply to multiple revisions but you can only have one Bug ID per > revision (this may be possible in the future but not at the moment). > > > Why wasn't this just implimented with a tag, why the seperate feature for > > something that should be conceptually the same? > > Bug IDs can refer to multiple revisions on multiple branches. A tag can > only refer to a single revision - tags aren't nearly flexible enough for > this purpose. > > Tony >