Hi All,
so after fixing "git remote get-url origin" to fail over to "git
remote show origin | filter and munge" the culture shock of "git commit -a"
(git commit does nothing ?!?!?) I have a VM that outputs a reasonable
version info:
/Users/eliot/oscogvm/build.macos32x86/squeak.cog.spur/CocoaFast.app/Contents/MacOS/Squeak
5.0 5.0.201606161953 Mac OS X built on Jun 16 2016 12:56:52 PDT Compiler:
4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57) [Production Spur VM]
CoInterpreter VMMaker.oscog-eem.1886 uuid:
d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016
StackToRegisterMappingCogit VMMaker.oscog-eem.1886 uuid:
d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016
VM: r201606161953 http://github.com/OpenSmalltalk/vm $ Date: Thu Jun 16
12:53:33 2016 -0700 $
Plugins: r201606161953 http://github.com/OpenSmalltalk/vm $
Which begs the question how do I differentiate this from something built
officially via Travis? Arguably the URL is wrong, and should only say "
http://github.com/OpenSmalltalk/vm" for travis builds, and perhaps should
just include my local hostname and current directory when I make any kind
of local modification. So the above would read
...
VM: r201606161953 McStalker:?users/eliot/oscogvm $ Date: Thu Jun 16
12:53:33 2016 -0700 $
Plugins: r201606161953 McStalker:?users/eliot/oscogvm $
Alternatively we could add another field, or modify one of the existing
fields to say "I'm official" however one would do that. I don't know how,
I just know we need this. I shouldn't be able to pollute the VM pool by
putting some VM on some site somewhere that i just happened to build after
several sherries and some cannabis brownies that looks to all intents and
purposes just like a VM built by our official Travis slaves. Hic. Chillin'
_,,,^..^,,,_
best, Eliot
Hi Laura, Hi Tim,
On Thu, Jun 16, 2016 at 10:09 AM, Laura Perez Cerrato <
lauraperezcerrato(a)gmail.com> wrote:
>
> Hi everyone,
>
> First of all, thanks a lot!
>
> Meaning to ask the same question as Serge, what's the preferred way of
> collaborating for anyone who's not a contributor? forking and then
> submitting a pull request?
>
thats on you, Tim, and I to update the README.md with a description of the
contributor and change staging process. I'm going to be checking out the
repository for the first time in a few minutes. I guess we can bat aroun
drafts between us using git itself, but perhaps email would be more
sensible ;-)
>
> Cheers!
>
> -Laura Perez Cerrato
>
> On 16 June 2016 at 06:10, Serge Stinckwich <serge.stinckwich(a)gmail.com>
> wrote:
>
>>
>> On Thu, Jun 16, 2016 at 9:24 AM, Tim Felgentreff
>> <timfelgentreff(a)gmail.com> wrote:
>> > Hi all,
>>
>> Very impressive work, Tim&Fabio ! The power of full-automation !
>>
>> > as of 7:30 UTC the entire history of the SVN up to SVN revision 3745 was
>> > migrated to GitHub. Automatic builds are running
>> > (https://ci.appveyor.com/project/timfel/vm/branch/Cog,
>> > https://travis-ci.org/OpenSmalltalk/vm) and binary artifacts are
>> uploaded
>> > (https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files).
>>
>> About uploading binary artifacts, this is something I asked and this
>> nice that Fabio
>> make it work :-)
>>
>> Apparently there is some problems with some artifacts that have a
>> double .zip extension.
>>
>> > Right now we have enabled all platform, object memory and bytecode set
>> > combinations that I found build scripts for - most work, but OS X 64-bit
>> > Sista is failing right now (32-bit works). At some point we'll have to
>> > decide which combinations to put into the CI config as "allowed
>> failures" to
>> > get a green badge :)
>> >
>> > Another thing for those not familiar with Git: Right now the entire
>> > repository is 360MB, including all history. Most of that is old images
>> that
>> > were at one point committed to SVN and that have been pulled into the
>> > repository. We could clean those out (removing them from the history) to
>> > make the repository smaller, but I felt ~400MB is still ok (albeit
>> > technically over the Github quota. We'll see of they complain). I would
>> like
>> > to ask everyone to stop committing large binary files into the
>> repository,
>> > however. Git is simply not very suited to dealing with binaries. If
>> there is
>> > a need for that, Github has support for git-lfs, which offers 1GB of
>> free
>> > storage with a 1GB bandwith limit per month. If we need more, we can
>> look at
>> > the different billing levels.
>> >
>> > If you're familiar with Git, the only new thing to watch out for is the
>> > updateSCSSVersions script as described in the README. It's not relevant
>> for
>> > the CI, but your own binaries will only show correct versions if this
>> script
>> > runs at appropriate times.
>> >
>> > If you are not familiar with Git and don't care, there are scripts for
>> > committing that should take care of everything as described in the
>> README.
>> > Again, let us know if anything doesn't work. The only difference vs SVN
>> to
>> > watch out for for you will be that the old scripts/svnci would commit
>> your
>> > changes to the server, whereas the scripts/gitci script only commits
>> them
>> > locally. You'll have to run `git pull` and `git push` to get them up to
>> the
>> > server.
>> >
>> > If you have any questions regarding the repository setup please don't
>> > hesitate to ask. You shouldn't be able to break anything, since we've
>> > disabled force pushes to both master and Cog (and thus any chance of
>> > destroying history).
>>
>> What is favorite way of contributing for people outside the vm team ?
>> pull-requests ?
>>
>> Regards,
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>
>
>
--
_,,,^..^,,,_
best, Eliot
Eliot Miranda uploaded a new version of Kernel to project The Trunk:
http://source.squeak.org/trunk/Kernel-eem.1029.mcz
==================== Summary ====================
Name: Kernel-eem.1029
Author: eem
Time: 16 June 2016, 4:17:52.232323 pm
UUID: 118ce27e-414e-4a37-940d-ce167fa5afb7
Ancestors: Kernel-mt.1028
Supply missing simulation methods for the new Mutex primitives and hence render through on code like the following funcitonal again:
Mutex new critical:
[[Object new]
on: Notification
do: [:noti| ]]
=============== Diff against Kernel-mt.1028 ===============
Item was added:
+ ----- Method: Mutex>>primitiveEnterCriticalSectionOnBehalfOf: (in category 'system simulation') -----
+ primitiveEnterCriticalSectionOnBehalfOf: effectiveProcess
+ "Primitive. Simulate primitiveEnterCriticalSection. The receiver
+ must be unowned or owned by the effectiveProcess to proceed.
+ Answer if the process is already owned by the current process."
+ <primitive: 186>
+ ^{ContextPart primitiveFailToken. nil}!
Item was added:
+ ----- Method: Mutex>>primitiveTestAndSetOwnershipOfCriticalSectionOnBehalfOf: (in category 'system simulation') -----
+ primitiveTestAndSetOwnershipOfCriticalSectionOnBehalfOf: effectiveProcess
+ "Primitive. Simulate primitiveEnterCriticalSection. Attempt to set the ownership
+ of the receiver. If the receiver is unowned set its owningProcess to the
+ effectiveProcess and answer false. If the receiver is owned by the effectiveProcess
+ answer true. If the receiver is owned by some other process answer nil."
+ <primitive: 187>
+ ^{ContextPart primitiveFailToken. nil}!
On Wed, Jun 15, 2016 at 05:01:36PM +0000, commits(a)source.squeak.org wrote:
> Laura Perez Cerrato uploaded a new version of Graphics to project The Trunk:
> http://source.squeak.org/trunk/Graphics-lpc.350.mcz
>
Yay! Thank you Laura for your contributions.
Dave
Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours:
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068216.html
Name: Kernel-mt.1028
Ancestors: Kernel-mt.1027
Extends EventSensor to be prepared for VMs to really send mouse-wheel events.
(Merges several peek* and prim* methods in EventSensor as a clean-up from the former InputSensor days.)
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068217.html
Name: Morphic-mt.1178
Ancestors: Morphic-mt.1177
Appendix to Kernel-mt.1028.
Support #wheelDelta in MouseWheelEvent instances for fine-granular scrolling. Do only raise flags for, e.g., #isWheelUp and #isWheelDown if the delta is above 120 units. Accumulate this in MouseWheelState. Wheel-up is every +120 and wheel-down is every -120.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068218.html
Name: ST80-mt.213
Ancestors: ST80-mt.212
Appendix to Kernel-mt.1028.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068219.html
Name: System-mt.833
Ancestors: System-mt.832
Make it possible to access the common request strings from other applications.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068220.html
Name: Morphic-mt.1179
Ancestors: Morphic-mt.1178
Add the world's Do-menu to the world main docking bar. Can be hidden via preferences.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068221.html
Name: Graphics-mt.349
Ancestors: Graphics-topa.348
Improves dark-map rendering of DejaVu Sans. Now, it does not look so bold anymore but is still way more readable on darker backgrounds than the bitmap version is.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068222.html
Name: Morphic-mt.1180
Ancestors: Morphic-mt.1179
Fixes a regression with event filterung and bubbling in general, which affects events sent to morphs that are submorphs of the hand. Escaping drag-and-drop, for example, where events are sent to the TransferMorph.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068223.html
Name: Morphic-mt.1181
Ancestors: Morphic-mt.1180
ixes regression in event dispatching and coordinate transformations. Do not reset transformation in the event copy delivered to submorphs. They need those for, e.g., double click, drag-and-drop, etc.
Our events do, more or less, not change after being created and initialized. The only exception is #wasHandled, #wasIgnored, and #position during event dispatching. Keep it that way. If you plan to change some event state in an event filter, create a new event instead and do not mess around with the current one.
=============================================
http://lists.squeakfoundation.org/pipermail/packages/2016-June/068224.html
Name: Graphics-lpc.350
Ancestors: Graphics-mt.349
Support for both the current version and the new version of JPEGReadWriter2Plugin
=============================================