On 04 Apr 2014, at 18:22, MartinW w...@fastmail.fm wrote:
When i add a new bug to the issue tracker it is automatically tagged as fix
if time. Am i supposed to change this label to higher priority if i think
it's appropriate -
Yes!
or is someone reviewing new entered bugs and assigning
Marcus Denker wrote:
Hi,
We are down to 17 open issues that are tagged “must fix” or higher:
https://pharo.fogbugz.com/f/filters/64/3-0-TODO
two of those have code that is in need of review.
Marcus
That is really great Marcus. Thanks for your efforts and those of the
When i add a new bug to the issue tracker it is automatically tagged as fix
if time. Am i supposed to change this label to higher priority if i think
it's appropriate - or is someone reviewing new entered bugs and assigning
priorities to them?
Anyway here's the bug:
give me 15’ ;)
On 09 Jan 2014, at 14:01, Marcus Denker marcus.den...@inria.fr wrote:
… so we finally managed to have no issues anymore that are
- fix review needed + pre-check by the monkey
- fix to integrate
Wow.. that never happened before ;-)
Marcus
If anyone wants the solution for
https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
before Jan 26, please remember Camillo is working on his PhD till then. (needs
reviewing)
Stephan
I do not get that. As far as I can tell, the fix is already integrated :).
Doru
On Fri, Jan 3, 2014 at 1:29 PM, Stephan Eggermont step...@stack.nl wrote:
If anyone wants the solution for
https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
Doru wrote:
I do not get that. As far as I can tell, the fix is already integrated :).
No, it needs to be resolved to Fix to be included.
Stephan
Hmm, strange. It was available in 30666, but it is not available anymore in
30669.
Was it reverted because it was not good, or was it because of another issue?
Doru
On Fri, Jan 3, 2014 at 2:14 PM, Stephan Eggermont step...@stack.nl wrote:
Doru wrote:
I do not get that. As far as I can tell,
Doru wrote:
Hmm, strange. It was available in 30666, but it is not available anymore in
30669.
Was it reverted because it was not good, or was it because of another issue?
It was never there. Did you by change load the slice in your 30666?
Stephan
Oops :)
Doru
On Fri, Jan 3, 2014 at 3:04 PM, Stephan Eggermont step...@stack.nl wrote:
Doru wrote:
Hmm, strange. It was available in 30666, but it is not available anymore
in 30669.
Was it reverted because it was not good, or was it because of another
issue?
It was never there. Did
Brilliant! I tested it, and it works fine.
Doru
On Thu, Jan 2, 2014 at 4:14 PM, Stephan Eggermont step...@stack.nl wrote:
I removed the preference setting, and made it a local action (Issue 10551)
Stephan
--
www.tudorgirba.com
Every thing has its own flow
PastedGraphic-1.png
Now, that the issue was fixed without me doing anything, I can reply.
I think we are going too much in the direction of discouraging opinions and
ideas on the basis that no code comes with them.
In our particular case, it seems to me that it was my little suggestion
that triggered the energy to
Now, that the issue was fixed without me doing anything, I can reply.
I think we are going too much in the direction of discouraging opinions and
ideas on the basis that no code comes with them.
Let us try to understand a bit. we have a LOT LOT LOT of duties for Pharo and
in addition we
On 30 Dec 2013, at 14:42, Sean P. DeNigris s...@clipperadams.com wrote:
Marcus Denker-4 wrote
- In monticello browser: when I select my project, all the repositories
available in Pharo are shown. As in Pharo 2.0, it should show only the
concerned repositories (2 or 3 max).
Yes, this was
On 30 Dec 2013, at 13:54, Sven Van Caekenberghe s...@stfx.eu wrote:
Hi Nicolai,
On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@web.de wrote:
for issue 12223
please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature,
I think this should not be a global preference at all. Most of the time,
you actually want to commit in the same repository where you always do.
Only from time to time do you need to switch and copy to another repo. So,
the preference should be per browser, not global.
Cheers,
Doru
On Tue, Dec
On 31 Dec 2013, at 11:58, Tudor Girba tu...@tudorgirba.com wrote:
I think this should not be a global preference at all. Most of the time, you
actually want to commit in the same repository where you always do. Only from
time to time do you need to switch and copy to another repo. So, the
Jannik wrote
- In a browser, when I did a change in the source code of a method,
then I select another method, the changes are lost, without asking if I want
to save changes.
Thanks Nicolai, for the fast results. I retested.
Resolved, Fix to Include
Stephan
I do not understand this reaction :(
Doru
On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker marcus.den...@inria.frwrote:
On 31 Dec 2013, at 11:58, Tudor Girba tu...@tudorgirba.com wrote:
I think this should not be a global preference at all. Most of the time,
you actually want to commit in
Marcus wrote:
On 31 Dec 2013, at 11:58, Tudor Girba [hidden email] wrote:
I think this should not be a global preference at all. Most of the time, you
actually want to commit in the same repository where you always do. Only
from time to time do you need to switch and copy to another repo.
Doru
The point of marcus is that we cannot take into account all wishes of
everybody: else we would not do anything else.
So if somebody thinks that something that is not in our critical path should be
changed he should submit code.
I have tons of ideas that could be implemented now since we
Stéphane Ducasse wrote
So if somebody thinks that something that is not in our critical path
should be changed he should submit code.
+1... and here is that person. The question in my post was: will anyone
speak up for this 'feature'? If not, I will be happy to revert to the old
behavior. While
Sean P. DeNigris wrote
and here is that person
I would've fixed it already, but since someone went through the trouble to
add a setting, I figured maybe there was a use case I was missing...
-
Cheers,
Sean
--
View this message in context:
Sean wrote:
I would've fixed it already, but since someone went through the trouble to add
a setting, I figured maybe there was a use case I was missing...
Please go ahead, I won't have any more time to do it today or tomorrow. Design,
no choice!
Stephan
On 30 Dec 2013, at 12:37, jannik.laval jannik.la...@gmail.com wrote:
Hi all,
I am porting Phratch in Pharo 3.0 and I have some problems with the
interface.
I uses a one-click Pharo3.0 #30664
Here is a list of what I have:
- in a debugger, it is not possible to do a Cmd-p to
On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@gmail.com wrote:
Hi all,
I am porting Phratch in Pharo 3.0 and I have some problems with the
interface.
I uses a one-click Pharo3.0 #30664
Here is a list of what I have:
- in a debugger, it is not possible to do a Cmd-p to
for issue 12223 https://pharo.fogbugz.com/default.asp?12223
please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects
(discard changes on close, lose changes when jump through the
Hi Nicolai,
On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@web.de wrote:
for issue 12223
please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects
(discard changes on
On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@web.de wrote:
for issue 12223
please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects
(discard changes on close, lose
Marcus Denker-4 wrote
- In monticello browser: when I select my project, all the repositories
available in Pharo are shown. As in Pharo 2.0, it should show only the
concerned repositories (2 or 3 max).
Yes, this was made on purpose and there is an issue that questions if that
idea was good:
Thank you for your answers guys.
Jannik
2013/12/30 Marcus Denker marcus.den...@inria.fr
On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@gmail.com wrote:
Hi all,
I am porting Phratch in Pharo 3.0 and I have some problems with the
interface.
I uses a one-click Pharo3.0 #30664
Hi Nicolai,
On 30 Dec 2013, at 13:26, Nicolai Hess nicolaih...@web.de wrote:
for issue 12223
please revert the changes done for editing history in Nautilus.
It makes more trouble than it helps.
It is a nice feature, but it is implementation has too many side effects
(discard changes
On 30 Dec 2013, at 12:44, Marcus Denker marcus.den...@inria.fr wrote:
On 30 Dec 2013, at 12:38, jannik.laval jannik.la...@gmail.com wrote:
Hi all,
I am porting Phratch in Pharo 3.0 and I have some problems with the
interface.
I uses a one-click Pharo3.0 #30664
Here is a list of
33 matches
Mail list logo
