On 03 Jan 2014, at 00:04, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Le 02/01/2014 20:37, Marcus Denker a écrit :
I always use “merge”. “Changes” will e.g. show all the changes towards
everything changed
in between, too.
For me this is weird, I can't understand the logic.
On 03 Jan 2014, at 10:32, Marcus Denker marcus.den...@inria.fr wrote:
On 03 Jan 2014, at 01:01, Sebastian Sastre sebast...@flowingconcept.com
wrote:
Changes reads
Merge writes
In order to make safe a potentially dangerous operation, the write is done
in two steps so the user can
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the changes of the slice.
In addition, there is still some bug that when e.g
2014/1/3 Hilaire Fernandes hilaire.fernan...@gmail.com
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the changes of the slice.
On 03 Jan 2014, at 12:04, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Le 03/01/2014 10:31, Marcus Denker a écrit :
From then the change was made *other* changes have been done.
“Change” will show *all* differences, both the ones other integrations
did to the package as well as the
On 02 Jan 2014, at 15:25, Marcus Denker marcus.den...@inria.fr wrote:
Hello,
We have some issues ready that nevertheless need to be reviewed by humans:
https://pharo.fogbugz.com/f/filters/45/Review
We know that they do not make tests fail and even pass some code critic tests.
Ok, this new to me, so I may not understand clearly.
I give a try and pointed Pharo 3.0 to a Slice I know about, SLICE 12495
on PolygonMoprh. I asked for the changes implication and see a lot not
related to PolygonMorph. Is it normal?
Hilaire
Le 02/01/2014 15:25, Marcus Denker a écrit :
Hello,
Hilaire wrote:
I asked for the changes implication and see a lot not
related to PolygonMorph. Is it normal?
The first comment is
mainly cleaning deadcode.
That should serve as a warning.
Most slices have a better focus, but there are a few
only describing the most important fix. Finer
On 02 Jan 2014, at 17:47, Hilaire Fernandes hilaire.fernan...@gmail.com wrote:
Ok, this new to me, so I may not understand clearly.
I give a try and pointed Pharo 3.0 to a Slice I know about, SLICE 12495
on PolygonMoprh. I asked for the changes implication and see a lot not
related to
Hi sven
We got an internal discussion on this topic with the same concerns. Komitter
was pushed because it does not touch existing code and because people like
mariano
where starting to code it in parallel. So we thought it was important for
people.
The idea is that we have some bugs to fix
Le 02/01/2014 20:37, Marcus Denker a écrit :
I always use “merge”. “Changes” will e.g. show all the changes towards
everything changed
in between, too.
For me this is weird, I can't understand the logic.
Merge: shows you the changes then let your merge
Change: shows some other sort of
Changes reads
Merge writes
In order to make safe a potentially dangerous operation, the write is done in
two steps so the user can confirm what is going to be written (or have a chance
to check if changes are the ones expected or not and abort without modifying
the code).
It's functionally
12 matches
Mail list logo
