[p4] Tracking changelist renumbering

[Jeff A. Bowles]

When in doubt, cheat....    run "p4 change" to update the change  
description
for the pending change, and even if you have to run 'p4 change' twice to
update the description with text like "<original pending chgnum was  
106>",
it'll be in the description.

Then "p4 changes -l" produces the list of changes and their  
descriptions,
including the "I was originally change 106" info.

   -Jeff Bowles

On Mar 9, 2007, at 8:31 AM, Brandon DuRette wrote:

> Hello all,
>
> I tried send this email to the list a few days ago, so I apologize  
> if this
> turns out to be a dup.  I was just in the process of subscribing to  
> the
> list, so I think it possibly got rejected, as possible spam.  In  
> any case,
> here's my question:
>
> In a trigger I would like to be able to detect when Perforce has  
> had to
> renumber a changelist.  For example, if the changelist in the user's
> workspace was @106, but after it was submitted it has become @109,  
> is there
> a way for a trigger to get both numbers?  I can use %change% to get  
> the
> @109, but I don't see any way to get to the old number.  Is there  
> way?  A
> workaround?
>
> The motivation is that I have some tools that integrate with  
> Perforce to get
> information about the changelist before submission.  I would like  
> to update
> this information to refer to the correct changelist number after  
> submission.
>
>
>
> Cheers,
> Brandon
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user