Backporting function in MC

> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> On Thu, Apr 23, 2009 at 9:49 PM, Alexandre Bergel
> <[hidden email]> 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
>
>

> On Thu, Apr 23, 2009 at 9:49 PM, Alexandre Bergel
> <[hidden email]> 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
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> 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 <[hidden email]>:
>> On Thu, Apr 23, 2009 at 9:49 PM, Alexandre Bergel
>> <[hidden email]> 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
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

>> I am glad you found this description useful. I am authoring a chapter
>> on Monticello for PharoByExample, and there is a section dedicated on
>> this functionality. However, I haven't been convinced this is a
>> feature really useful since I know no-one who used it.
>
> Avi wrote that feature at ESUG in the car somewhere between Hannover
> and Köethen. We were discussing the implementation several times
> during that 8 hour drive. I used it a couple of times.
>
> What I find easier (because I don't have to load the other version) is
> to open a merge dialog with the other version and selectively pick
> some changes and click on 'Install' in the context menu. Then
> close/cancel the merge dialog and click on 'Adapt' and select the just
> merged version. I don't exactly know about the semantic differences
> between the two approaches, could well be that my approach ends up
> with a nightmare later on but so far it worked well for me.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Thanks Lukas,
>
> Alexandre
>
>
> On 24 Apr 2009, at 14:38, Lukas Renggli wrote:
>
>>> I am glad you found this description useful. I am authoring a  
>>> chapter
>>> on Monticello for PharoByExample, and there is a section dedicated  
>>> on
>>> this functionality. However, I haven't been convinced this is a
>>> feature really useful since I know no-one who used it.
>>
>> Avi wrote that feature at ESUG in the car somewhere between Hannover
>> and Köethen. We were discussing the implementation several times
>> during that 8 hour drive. I used it a couple of times.
>>
>> What I find easier (because I don't have to load the other version)  
>> is
>> to open a merge dialog with the other version and selectively pick
>> some changes and click on 'Install' in the context menu. Then
>> close/cancel the merge dialog and click on 'Adapt' and select the  
>> just
>> merged version. I don't exactly know about the semantic differences
>> between the two approaches, could well be that my approach ends up
>> with a nightmare later on but so far it worked well for me.
>>
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>