If you meant that the two developers were using the same branch, and you
REALLY wanted to do this, and assuming multiple interspersed commits by
each developer, you could probably write a script that went from file to
file, determined who had made each commit, and backed the changes out.
This could be a pain as your script would require some sort of state
saving and/or user intervention if it encountered any merging conflicts.
See Sean Cavanaugh's response to your other post to understand how to back
changes out.
If you meant they were each working on their own branch, Sean's solution
should work. You just back out the undesirable branch and not the other.
Future preparation? Have any change you wish to consider a single "unit"
(bug-fix, enhancement, whatever) for implementation and testing purposes
assigned to its own branch. Note Sean's advice about tagging any branch
with an additional "base" tag upon branch creation and after merging it
anywhere. If you can't tell CVS where your start point and end point are
for the back-out, you won't be able to back changes out.
Derek R. Price
CVS Solutions Architect
303.554.8291
[EMAIL PROTECTED]
http://alumni.engin.umich.edu/~oberon/resume.html
Troy Hall wrote:
> I branched our development trunk for two developers. The developers
> develop. One developer's code passed QA. The other's did not. I
> would like to leave the first developer's code in the branch, but I'd
> like to remove the other developer's code.
>
> Does anyone have any suggestions about what CVS function could offer me
> some assistance in doing this? If not, can you suggest how I could
> better prepare in the future?
