Thank you for this useful link. So the procedure described by Avi is

"At various points there have been requests that when merging versions,
you be able to select only some of the changes to merge.  You can use
the Backport facility to do this as follows:

- load the version you want to merge some of the changes from
- backport those changes to the common ancestor with the version you
want to merge into
- save this backported version
- load your version, and merge in the backport

Eventually, it would of course be nice to have a more automated UI for
doing that..."

This is a feature I asked very recently:
http://article.gmane.org/gmane.comp.lang.smalltalk.sapphire.devel/7440/match=merge

So I feel free to give my feeling:
1) The whole procedure seems overkill to me versus implementing same
functionality in merge tool
2) There are cases when I do not want to load the other version
because I know it would break my image
3) in some cases the common ancestor is far away or out of reach
(imagine I want to compare two squeak forks)

Nicolas

2009/4/24 Damien Cassou <[email protected]>:
> On Thu, Apr 23, 2009 at 9:49 PM, Alexandre Bergel
> <[email protected]> wrote:
>> Dear All,
>>
>> Are there any of you who already used the backporting function of
>> Monticello? It has been there for several years already. Enough time
>> to prove its usefulness.
>
> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/082094.html
>
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to