--- Begin Message ---
Sure, here you are.
https://github.com/pharo-project/pharo-launcher/issues/355
> On Sep 15, 2019, at 2:14 PM, Christophe Demarey
> wrote:
>
> Hi Todd,
>
> Thanks for the report.
> Could you create an issue on Github and explain the way to reproduce?
>
>
Hi Todd,
Thanks for the report.
Could you create an issue on Github and explain the way to reproduce?
https://github.com/pharo-project/pharo-launcher/issues
Regards,
Christophe
> Le 15 sept. 2019 à 21:04, Todd Blanchard via Pharo-dev
> a écrit :
>
>
> De: Todd Blanchard
> Objet: Pharo
--- Begin Message ---
I just downloaded the latest Pharo Launcher.
It is throwing some errors.
--- End Message ---
There is a new Pharo build available!
The status of the build #737 was: FAILURE.
The Pull Request #4598 was integrated: "4597-Adding-string-executable-examples"
Pull request url: https://github.com/pharo-project/pharo/pull/4598
Issue Url: https://github.com/pharo-project/pharo/issues/4597
There is a new Pharo build available!
The status of the build #736 was: FAILURE.
The Pull Request #4600 was integrated: "2404-Morph-Theme"
Pull request url: https://github.com/pharo-project/pharo/pull/4600
Issue Url: https://github.com/pharo-project/pharo/issues/2404
Build Url:
> On 15 Sep 2019, at 13:31, Hilaire wrote:
>
> Question: What is exactly "current commits of your image". I understand
> it in two ways:
The image you download is somewhere based on a commit from Pharo.
You may have got some extra changes in addition (for example if we have run
a code
Question: What is exactly "current commits of your image". I understand
it in two ways:
1. Sync the local repo with the commits to match with the code in this
image (I think it is this one)
2. Sync local repo with the current commits (yes latest) for this image
in its remote repo
Thanks
with some copy edit
tep 6: Why you do not need to resync your fork with the pharo repo?
No you do not need to explicitly resync your fork. Why? Because when you push
your commits, you push also the Pharo commits. But let us look at it in details:
When you download an image (imagine that this
Step 6: Why you do not need to resync your fork with the pharo repo?
No you do not need to explicitly resync your fork. Why? Because when you push
your commits, you push also the Pharo commits. But let us look at it in
details: When you download an image (imagine that this image contains the
Hilaire
When you download an image (it can come from mars) so the system
does not know, where the sources are, to which commit it should point.
So this is why you should either clone again or point to the source.
Once you have downloaded or pointed to your fork (which can be old from a
What should I do next ?
I install a newer P8, point the image repo to my existing repo in the
local filesystem. Is it right?
It seems I need to repair, but I don't understand why the repair dialog
say and what option to pick up. I can't anticipate the consequences.
Glossary, please (the one
11 matches
Mail list logo
