> Gerardo Richarte wrote:
> 
> > you can remove all methods
> > with a timestamp newer than the current stamp for that same method. As a
> > result, you get a changelist with only those methods on the .cs file you
> > opened, that whould overwrite newer versions if filed in.
> 
> I'd just like to note, without diminishing this effort, that simple as this
> solution is it doesn't solve this problem completely--I'm just saying this
> because it is a problem which I'd very much like to see addressed. If you
> develop code for version A (or update older code for it) during the period
> when also version A+1 is developed--the way things currently work, in other
> words--then not all changed methods will be caught by this simple date test,
> because also methods with older dates than yours may belong to version A+1
> (and perhaps vice versa).
> 
> hoping that someone has a comprehensive solution in the works,

Another stab at this:
The Change Versioner takes a change set and adds a prior stamp for every
method, that was already in the system and has been changed by the
change set. This way you can record which version your changes were
relative to.


Example:
Suppose you have a change set for 2.7 and want to port it into 2.9. What
you would like to know is which of system methods you changed in your
change set have changed since then.
What you need to do:
FileIn this change set into the old system. Run the ChangeVersioner on
your change set.
Load the new change set file into a change list in the new system. Run
'select conflicts with prior versions'. All methods that have a prior
stamp different from the one in your change set will be selected.

Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: changeVersioner.zip
Type: application/x-zip-compressed
Size: 3588 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20010103/c9b73417/changeVersioner.bin