Backporting operation in Monticello

Dear List,

What is the exact meaning of the Backport button in Monticello?
The method MCWorkshopCopy>>backportChangesTo: suggest that a package  
is "adapted" to one of its ancestor. Is there a difference with  
loading a new version of its package?

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Hello Alex,

with backporting you can choose the changes which should be loaded.  
Loading the version means that all changes are applied. That means  
that you can do "cherry picking" with backporting.

Best,
Robert


Am Jan 7, 2008 um 1:42 PM schrieb Bergel, Alexandre:

On Jan 7, 2008 1:42 PM, Bergel, Alexandre <[hidden email]> wrote:
> What is the exact meaning of the Backport button in Monticello?
> The method MCWorkshopCopy>>backportChangesTo: suggest that a package
> is "adapted" to one of its ancestor. Is there a difference with
> loading a new version of its package?

http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/082094.html

--
Damien Cassou

Hi Alex,

Bergel, Alexandre wrote:

> What is the exact meaning of the Backport button in Monticello?
> The method MCWorkshopCopy>>backportChangesTo: suggest that a package is
> "adapted" to one of its ancestor. Is there a difference with loading a
> new version of its package?

I did the same question recently and just tried it. Backport actually
change a parent version from which you track changes. It seems that is
useful if you change repositories often or (as I use it) to publish
first on local cache, test it, then  backport to last SqueakSource
version and then finally publish new version there. It is similar to
Reconcile  with a database on VW's Store.

Best regards
Janko


--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si

Hi Alex,


I will give the general idea, since I don't remember the implementation.


The idea is to cherry pick changes. Suppose you are the main maintainer
of a package, and X is a contributor. Suppose makes two sets of
independent changes A and B, each in a separate version, where B has A
as an ancestor. Suppose that you only like A, then you simply merge A,
and ignore B. What happens if you only like the changes in B? if you
merge in B, you also get the changes in A. If you undo those manually,
you have imprecise history management that will take its revenge later.


In general, Backport creates a version that has only B, without A, and
allows you to merge it in. IIRC, it handles somewhat more general
situations, too.


Daniel


Bergel, Alexandre wrote:

> Dear List,
>
> What is the exact meaning of the Backport button in Monticello?
> The method MCWorkshopCopy>>backportChangesTo: suggest that a package
> is "adapted" to one of its ancestor. Is there a difference with
> loading a new version of its package?
>
> Cheers,
> Alexandre

Thanks to all of you!

> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004- 
> September/082094.html

The link above is the more complete description.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.