March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Peter UhnÃ¡k

> > No, freeze was 18 days agoâ¦ is 12 days to release. >> > Aha, I confused the two. Anyway, the github support in Pharo4 is as it was in Pharo3: kind of broken > :( Well I work from bleeding edge (more or less), so if it will be in early Pharo 5 it's fine. In the meantime, can I load it myself? Where is the repo? Will it break anything? Thanks, Peter

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Thierry Goubier

Le 19/03/2015 20:42, Esteban Lorenzano a Ã©crit : > >> On 19 Mar 2015, at 20:39, Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> Question now: is it still viable to include the latest Metacello >> in Pharo 4 despite the freeze? >> >> It is still 12 days till freeze; are there any issues associated with >> it? Because this is a bug fix, not a feature. Unless its bundled with >> a lot of other stuff. > > No, freeze was 18 days agoâ¦ is 12 days to release. > Now we just accept bugfixes (and a new release of Metacello is far more > than a bugfix). Ok, thanks. Then I won't spend my evening looking at it ;) Anyway, the github support in Pharo4 is as it was in Pharo3: kind of broken :( Thierry

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Thierry Goubier

Le 19/03/2015 20:39, Peter UhnÃ¡k a Ã©crit : > Question now: is it still viable to include the latest Metacello in > Pharo 4 despite the freeze? > > It is still 12 days till freeze; are there any issues associated with > it? Because this is a bug fix, not a feature. Unless its bundled with a > lot of other stuff. I'll make a diff to the latest Pharo4 to check. I believe Dale suggested to StÃ©phane he could upgrade easily. It corrects at least one bug :) and probably a few, hard to solve, dependencies issues in complex configurations, from past messages. Thierry

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Esteban Lorenzano

> On 19 Mar 2015, at 20:39, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Question now: is it still viable to include the latest Metacello in Pharo 4 despite the freeze? > > It is still 12 days till freeze; are there any issues associated with it? Because this is a bug fix, not a feature. Unless its bundled with a lot of other stuff. No, freeze was 18 days agoâ¦ is 12 days to release. Now we just accept bugfixes (and a new release of Metacello is far more than a bugfix). Esteban > > Peter

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Peter UhnÃ¡k

> > Question now: is it still viable to include the latest Metacello in Pharo > 4 despite the freeze? > It is still 12 days till freeze; are there any issues associated with it? Because this is a bug fix, not a feature. Unless its bundled with a lot of other stuff. Peter

March 19, 2015

Re: [Pharo-dev] Duration year

by Hilaire

Le 19/03/2015 19:03, Sean P. DeNigris a Ã©crit : > Esteban A. Maringolo wrote >> The problem is "unsolvable" as it is now, IMHO, because all the chronology >> objects are based on "offset" representations (since an epoch) > The more I work with Dates, the more I feel that, unless we do something > "correct" like Chalten or GenericYear, years should be totally removed from > Duration. Maybe for Pharo 5.0? > Agreed we can improve the situation. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Thierry Goubier

Hi Peter, after raising an issue on FileTree, Dale pointed out this was corrected in the latest Metacello (which is not included in Pharo 4). Question now: is it still viable to include the latest Metacello in Pharo 4 despite the freeze? Thierry Le 19/03/2015 01:31, Peter UhnÃ¡k a Ã©crit : > Hi, > > the repository specification > 'github://<user name>/<project name>[:comitish]/<path to filetree repo>' > doesn't support slashes in commitish. > > For example if I have branch named 'feature/something', or > 'hotfix/otherthing' it breaks. > > There may be conflict also with path (imagine having branch > repository/repository and and actual folder called repository), so this > may require something special... like having another separator... i.e. > <project name>[:commitish[:]]/<path to filetree repo>? (Optional ending > colon.) > > Peter

March 19, 2015

Re: [Pharo-dev] Duration year

by Sean P. DeNigris

Esteban A. Maringolo wrote > The problem is "unsolvable" as it is now, IMHO, because all the chronology > objects are based on "offset" representations (since an epoch) The more I work with Dates, the more I feel that, unless we do something "correct" like Chalten or GenericYear, years should be totally removed from Duration. Maybe for Pharo 5.0? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Duration-year-tp4791727p4813313.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 19, 2015

Re: [Pharo-dev] Number>>#percent

by Sean P. DeNigris

Tudor Girba-2 wrote >> Although I must say that it should have been >> ^ self / 100 Good point. Let's not introduce an incorrect feature! Issue 15165: Number>>#percent shouldn't force to Float Fix in inbox. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Number-percent-tp4805988p4813236.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 19, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40567 Home: https://github.com/pharo-project/pharo-core

March 19, 2015