[p4] Revert a changelist
Robert Cowham
robert at vaccaperna.co.uk
Thu Jul 12 17:27:58 PDT 2007
In principle you are correct, without the obliterate someone has to remember
outside Perforce that the integration should be redone (in which case an
integ -f would do it).
Not a nice situation, and also one that I would not attempt to make *too*
easy for users - i.e. I would encourage them to think and test before
submitting an integrate, rather than just promising them an easy fix
afterwards if they get it wrong.
In some ways it would be nice if Perforce offered an option to do an
integrate which "undid" a previous integrate - didn't change the contents of
files but removed the integrate records.
We can always suggest to support...
Robert
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Jamie.Echlin at barclayscapital.com
> Sent: 12 July 2007 16:14
> To: steve at vance.com
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Revert a changelist
>
> Hi Steve,
>
> Didn't find anything in the public depot, but thanks.
>
> > I can provide more help on the others. The revert of a branch
> operation would be a delete as the only option short of obliterate.
>
> The problem with this is, next time the integration is done
> you will get "all revisions already integrated". What you
> want to happen is for the integ to happen again, as though
> the initial changelist had never happened. I can't see anyway
> around this without an oblit.
>
> Cheers, jamie
>
More information about the perforce-user
mailing list