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

New Versionner Tool and Authentication

by Sean P. DeNigris

It seems maybe the "commit Xyz patch" tool is creating new instances of repositories instead of using the existing ones? Even though I am logged into sthub/Pharo/TxText, when I try to commit a config and new package versions for packages, dialogs pop up to enter my username and password, and even if I fill them out the credentials don't seem to be accepted. After cancelling, I can copy them over from my cache in the MC browser, so I'm definitely logged in. Any ideas? ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Esteban Lorenzano

do you guys know that if you press in the link provided, for example: https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a340… <https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a340…> you will have all the diffs well organised and for free? Esteban ps: in fact, if possible, I wouldnât publish even the list of files changedâ¦ just the commit message and the link > On 03 May 2015, at 18:23, stepharo <stepharo(a)free.fr> wrote: > > >> Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;) >> >> > Yes I would love that too. > I just want to compile a list of changes automatically. > May I can do in the scriptLoader instead of reparsing git. >

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by stepharo

> Code diffs would be more valuable, but adopting the tools of file > lovers must come with a cost ;) > > Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.

May 3, 2015

[pharo-project/pharo-core]

by GitHub

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

May 3, 2015

[pharo-project/pharo-core] cf09b1: 50029

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cf09b156e5bc943d6b99a34016d64ac0e6e972b5 https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a340… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-03 (Sun, 03 May 2015) Changed paths: M Morphic-Widgets-Tabs.package/TabManager.class/instance/private-actions/deleteSelectedTabs.st M NativeBoost-Core.package/NBExternalAddressType.class/instance/emitting code/pushAsPointer_.st M NativeBoost-Core.package/NBExternalAddressType.class/instance/emitting code/pushAsValue_.st M NativeBoost-Core.package/NBExternalObjectType.class/instance/emitting code/pushAsPointer_.st M NativeBoost-Core.package/NBExternalObjectType.class/instance/emitting code/pushAsValue_.st M NativeBoost-Core.package/NBExternalStructureType.class/instance/emitting code/pushAsPointer_.st A NativeBoost-Core.package/NBExternalType.class/instance/emitting code/coerceNilToNull_oop_doneLabel_.st M NativeBoost-Core.package/NBExternalType.class/instance/emitting code/pushAsPointer_.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkConditionReflectiveDisable.st M Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleMethod.st M Reflectivity.package/MetaLink.class/instance/ast/hook.st A Reflectivity.package/MetaLink.class/instance/ast/valueInContext_.st A Reflectivity.package/MetaLink.class/instance/ast/wrapCondition_.st R Reflectivity.package/MetaLink.class/instance/meta eval/valueInContext_.st A Reflectivity.package/MetaLink.class/instance/reflecive api/disable.st A Reflectivity.package/MetaLink.class/instance/reflecive api/enable.st A Reflectivity.package/MetaLink.class/instance/testing/hasMetaLevel.st A Reflectivity.package/MetaLink.class/instance/testing/hasReifiedCondition.st A Reflectivity.package/RFCondition.class/README.md A Reflectivity.package/RFCondition.class/class/as yet unclassified/for_.st A Reflectivity.package/RFCondition.class/definition.st A Reflectivity.package/RFCondition.class/instance/accessing/condition_.st A Reflectivity.package/RFCondition.class/instance/accessing/linkCondition_.st A Reflectivity.package/RFCondition.class/instance/enable%2Fdisable/disable.st A Reflectivity.package/RFCondition.class/instance/enable%2Fdisable/enable.st A Reflectivity.package/RFCondition.class/instance/evaluating/value.st A Reflectivity.package/RFCondition.class/instance/initialization/intitialize.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script637.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script638.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50028.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50029.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50029 15334 Closing tabs with ctrl+w shortcut sometimes throws error https://pharo.fogbugz.com/f/cases/15334 15479 Condition Reification https://pharo.fogbugz.com/f/cases/15479 14479 Enable nil to NULL coercion for NBExternalObjectType https://pharo.fogbugz.com/f/cases/14479 http://files.pharo.org/image/50/50029.zip

May 3, 2015

Re: [Pharo-dev] PluggableTextMorph vs PluggableTextEditorMorph

by Nicolai Hess

2015-05-02 9:50 GMT+02:00 stepharo <stepharo(a)free.fr>: > No idea but if the difference is that small then this is clear that we > should remove one. > > What is the difference between (or different use cases for) >> PluggableTextMorph and PluggableTextEditorMorph ? >> >> Do we need both? >> >> The only difference I see: >> You can not toggle enabled/disabled a PluggableTextMorph, >> whereas a PluggableTextEditorMorph can be disabled. >> >> >> >> nicolai >> >> > Now I see, they use different editorclasses too (TextEditor vs. SmalltalkEditor).

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Ben Coman

> > On Sun, May 3, 2015 at 4:15 AM, stepharo <stepharo(a)free.fr> wrote: > >> Hi >> >> could we put the log of the commit on top before the touched files? >> >> Stef >> >> > On Sun, May 3, 2015 at 10:46 PM, Ben Coman <btc(a)openinworld.com> wrote: > I tried with this, but didn't know how to push it further... > https://github.com/github/github-services/compare/master...bencoman:master > > cheers -ben > Whoops. Seems I missed actually submitting a pull request for the change. Now lets see how it goes. cheers -ben

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Ben Coman

I tried with this, but didn't know how to push it further... https://github.com/github/github-services/compare/master...bencoman:master cheers -ben On Sun, May 3, 2015 at 4:15 AM, stepharo <stepharo(a)free.fr> wrote: > Hi > > could we put the log of the commit on top before the touched files? > > Stef > >

May 3, 2015

Re: [Pharo-dev] Pharo Inbox Link pointing to Pharo40 Inbox still

by Cyril Ferlicot

I corrected it. On 3 May 2015 at 13:55, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > Ah, that's why I commited my changes to version 4 > > On Sun, May 3, 2015 at 6:26 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> On >> >> http://pharo.org/contribute-propose-fix >> >> in "Prerequisites" the "Pharo Inbox" link points to the pharo40inbox >> instead of pharo50inbox. >> >> Norbert >> > -- Cheers Cyril Ferlicot

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Marcus Denker

> On 03 May 2015, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I think it is not possible (thatâs github stuff, not ours)â¦ at least it was not possible 1.5yr ago when we did it with Camilo. > but I will take another look, in case things changed. > I think there is a chance to do it with this magical thing: https://zapier.com <https://zapier.com/> It seems to have an email parser that is very powerfulâ¦ so github would send there and then zappier could send a modified mail onwards (and swallow the branch one). Marcus > Esteban > >> On 03 May 2015, at 04:41, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> stepharo wrote >>> could we put the log of the commit on top before the touched files? >> >> +1. But Nicolas wants to know if he can view the files in his favorite >> editor, `#(vim emacs) atRandom`ha ha >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-i… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

May 3, 2015