Hi
Normally each time a PR is integrated in a book, the CI is generating the PDF.
https://github.com/SquareBracketAssociates/Booklet-uFFI/releases
So what you can do is to not bother and copy-edit and we fix the corresponding
pillar
if you break it.
Stef
> On 24 Sep 2019, at 10:34,
On 2019-09-23 23:25, Sean P. DeNigris wrote:
> Jan Vrany wrote
>> What is the correct workflow to end up with:
>> --- A --- B --- C --- D --- E
>
> Not in front of an image, but IIU/RC if you’re seeing “detached”, click
> repair, then the option where you use the repository version (which I think
There is a new Pharo build available!
The status of the build #779 was: FAILURE.
The Pull Request #4717 was integrated: "Fixed typo in category"
Pull request url: https://github.com/pharo-project/pharo/pull/4717
Issue Url: https://github.com/pharo-project/pharo/issues/fixed
Build Url:
> On 24 Sep 2019, at 14:54, Sean P. DeNigris wrote:
>
> Marcus Denker-4 wrote
>> we coud back port the fix...
>
> That would be great if you think it's fairly safe. Although personally I
> could roll back my stateful traits use until P8 since I just started using
> them. BTW what is the ETA
Marcus Denker-4 wrote
> we coud back port the fix...
That would be great if you think it's fairly safe. Although personally I
could roll back my stateful traits use until P8 since I just started using
them. BTW what is the ETA for P8 release?
-
Cheers,
Sean
--
Sent from:
There is a new Pharo build available!
The status of the build #778 was: FAILURE.
The Pull Request #4708 was integrated: "4706 convenient method to instantiate a
form from a base64 encoded string"
Pull request url: https://github.com/pharo-project/pharo/pull/4708
Issue Url:
There is a new Pharo build available!
The status of the build #777 was: FAILURE.
The Pull Request #4711 was integrated: "Add-copy-title-command-to-windows"
Pull request url: https://github.com/pharo-project/pharo/pull/4711
Issue Url: https://github.com/pharo-project/pharo/issues/Add
Build
There is a new Pharo build available!
The status of the build #776 was: SUCCESS.
The Pull Request #4699 was integrated: "2174-withoutDuplicates"
Pull request url: https://github.com/pharo-project/pharo/pull/4699
Issue Url: https://github.com/pharo-project/pharo/issues/2174
Build Url:
we coud back port the fix...
> On 24 Sep 2019, at 08:38, Max Leske wrote:
>
> Hi,
>
> As I wrote to Sean on Discord, Marcus fixed that bug during ESUG. I realize
> now, however, that it is only fixed in Pharo 8. I would need to write a patch
> for Fuel to make it work in Pharo 7.
>
>
Hi Ted,
I split this in a separate thread to avoid noise :)
> El 23 sept 2019, a las 23:14, Brainstorms escribió:
>
> Guillermo,
>
> I'm interested in helping, but at this point, I think I'd be most helpful
> working at improving documentation (mainly editing) rather than working on
> Pharo
Jan Vrany wrote:
> Hi,
>
> I'm experiencing difficulties (code loss, even) when trying to
> commit code using Iceberg.
>
> I have a project with consist of some Pharo code and some
> C++ code. Both parts kind of depend on each other.
>...
> Any suggestions?
Hi,
As I wrote to Sean on Discord, Marcus fixed that bug during ESUG. I
realize now, however, that it is only fixed in Pharo 8. I would need to
write a patch for Fuel to make it work in Pharo 7.
Alternatively, you could include the patch in your code, then Fuel
should work.
Cheers,
Max
There is a new Pharo build available!
The status of the build #775 was: FAILURE.
The Pull Request #4689 was integrated:
"4686-code-completion-not-working-properly-on-inspectors"
Pull request url: https://github.com/pharo-project/pharo/pull/4689
Issue Url:
Hi Sean,
On Mon, 23 Sep 2019 at 23:37, Sean P. DeNigris wrote:
>
> Sean P. DeNigris wrote
> > I see commit 1dd... back in March 2018 says it should work
>
> Investigating a bit further, maybe the problem is in Pharo, because another
> test in Pharo 8 didn't show the issue.
14 matches
Mail list logo
