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 email@example.com.
Jan Keirse wrote: > "Arthur Barrett" <arthur.barrett at march-hare.com> schreef op 14/04/2008 > 01:06:02: > > >> Jan, >> >> >>> Probably a job matches a commitId (although I haven't looked into >>> commitId's yet). >>> >> Yes from the sounds of it that is exactly what you should be using. And >> yes - if you want to 'rollback' a commit you certainly can using the >> commit id. >> >> cvs update -e -j @commitid -j "@<commitid" >> >> When you commit this a mergepoint will also be creating which shows in >> the history that the change was rolled back. >> >> Note: there are also 'user defined changesets' which can span multiple >> commits, see "cvs commit -B jub-number". >> > > That's exactly what I need to make my life easy, but I'd have to be able > to pass it to tortoiseAct, because we use it to do the commit. > To use 'commit -B', simply check 'Mark bug' in the Commit dialog. You cannot get TortoiseCVS to use -e with 'cvs update', but you can enter '@commitid' and '@<commitid' in the Merge dialog. -Torsten