On Tue, 13 Nov 2018 at 05:42, Hans-Martin Mosner
wrote:
> I put it on ss3 because I'm not yet familiar with the way Pharo uses
> github. Will look into it later.
>
> I'm unsure how git repositories are used in the Pharo context. Do you use
> them just like you use git normally (i.e. I
> use my
Hi Norbert,
I just converted the repository to git few days ago:
https://github.com/VincentBlondeau/Tabular
I missed to inform you on the mailing list. A thing that is now done!
Thanks,
Vincent
-Original Message-
From: Pharo-dev On Behalf Of Norbert Hartl
Sent: Wednesday, November 28,
> On 28 Nov 2018, at 12:25, Esteban Lorenzano wrote:
>
> Ah, I forget to say that this change we enter in effect today :)
Ok, maybe tomorrow since I needed to refresh my groovy knowledge ;)
Esteban
> May the force be with us.
>
> Esteban
>
>> On 28 Nov 2018, at 12:25, Esteban Lorenzano >
Is there any progress on this? Can you tell the S3 url you are using?
Do you need help to put it on github?
Norbert
> Am 12.11.2018 um 22:41 schrieb Hans-Martin Mosner :
>
> I put it on ss3 because I'm not yet familiar with the way Pharo uses github.
> Will look into it later.
>
> I'm
Christophe Demarey wrote:
> Why not following git flow?
Because git flow has branches that don’t add value?
Stephan
There is a new Pharo build available!
The status of the build #1419 was: SUCCESS.
The Pull Request #2018 was integrated:
"22702-support-before-after-intead-on-RBCascadeNode"
Pull request url: https://github.com/pharo-project/pharo/pull/2018
Issue Url: https://pharo.fogbugz.com/f/cases/22702
Ah, I forget to say that this change we enter in effect today :)
May the force be with us.
Esteban
> On 28 Nov 2018, at 12:25, Esteban Lorenzano wrote:
>
> Ok, a new pass onto this, I decided that having just dev-Etc. branches and
> not having a clear stable one may lead to confusion.
>
Ok, a new pass onto this, I decided that having just dev-Etc. branches and not
having a clear stable one may lead to confusion.
After checking some projects on GitHub, seems that what they do is to name
their branches just with the version, not with “dev” (like, for example
"gtk-2.22”).
So, I
> Am 28.11.2018 um 09:38 schrieb Christopher Fuhrman
> :
>
> Hello,
>
> In Pharo 6.1 I have got Iceberg working and love the interface to GitHub.
> Thanks to the Rmod folks for all the patient answers to my newbie questions.
>
> However, most of my development remains in playground
Hi,
> On 28 Nov 2018, at 09:38, Christopher Fuhrman
> wrote:
>
> Hello,
>
> In Pharo 6.1 I have got Iceberg working and love the interface to GitHub.
> Thanks to the Rmod folks for all the patient answers to my newbie questions.
>
> However, most of my development remains in playground
Hello,
In Pharo 6.1 I have got Iceberg working and love the interface to GitHub.
Thanks to the Rmod folks for all the patient answers to my newbie
questions.
However, most of my development remains in playground scripts, and as far I
understand, it's not possible to put them under version
11 matches
Mail list logo
