I'm just a reader here, but I'm a developer on other (software) stuff and
somehow used to HEAD and MASTER.
Those of you that feel offended by the word master, should go and lookup the
origin of that word and its roots.
Picking up on Andy's comment, yes, the false interpretation comes clearly from
abusive use of that word in colonial history
I guess I'm missing where that petition comes from, but it sounds somehow
stupid to me and I go full with Chris, saying it's an absolute unnecessary task
putting effort in changes that doesn't do anything good to the project.
ju
________________________________
From: emc-developers-requ...@lists.sourceforge.net
<emc-developers-requ...@lists.sourceforge.net>
Sent: Thursday, July 29, 2021 12:19 AM
To: emc-developers@lists.sourceforge.net <emc-developers@lists.sourceforge.net>
Subject: Emc-developers Digest, Vol 183, Issue 30
Send Emc-developers mailing list submissions to
emc-developers@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/emc-developers
or, via email, send a message with subject or body 'help' to
emc-developers-requ...@lists.sourceforge.net
You can reach the person managing the list at
emc-developers-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Emc-developers digest..."
Today's Topics:
1. Re: Realtime-components for named/numbered parameters in
G-Code (from Re: Question for the devs) (Les Newell)
2. Re: Using `main` instead of `master` branch (Jeff Epler)
3. Re: Using `main` instead of `master` branch (andy pugh)
4. Re: Using `main` instead of `master` branch (Alec Ari)
5. Re: Using `main` instead of `master` branch (Chris Morley)
----------------------------------------------------------------------
Message: 1
Date: Wed, 28 Jul 2021 13:54:39 +0100
From: Les Newell <les.new...@fastmail.co.uk>
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Realtime-components for named/numbered
parameters in G-Code (from Re: Question for the devs)
Message-ID: <b11fcca5-2d62-2fe8-a540-a4aaf94a5...@fastmail.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
It shouldn't be too hard to implement something like:
USER_PARAM_5021 = name_of_hal_pin
However we already have M66 and M67 which can talk to HAL pins.
Les
On 28/07/2021 07:42, Stefan Freisei Muehlbacher wrote:
> Just an idea for a more flexible extension.
>
> [SomwareInTheINI]
>
> [RS274NGC]
>
> USER_PARAM_5021 = name_of_realtime_component
>
> name_of_realtime_component has to calculate that value, and then its
> avaiable in as #5021 in the interpreter.
>
> I don?t know for sure if every value for abs position is avaiable in
> the RT-Components. But i think would be a great way to add more of
> such values in a flexible way without changes in source-code. Just
> like HAL-RT-componets.
>
> With such a solution some of my huge/complicated macros would be very
> much handier. Additionally it would be possible to get better
> debugging by writing out some values into HAL and monitor them with
> halscope for example.
>
> Aaaaaaaaand, by this way it would be possible to write out values to
> hal in a easier way. (Do i correctly remember its not possible by
> default and we have to use M-Codes?)
>
> Don?t know anything about how much code must be changed in the
> "untouchable interpreter code" and about side effects, but as more as
> i think about this extension as more ideas i get how many things could
> be made easier with that.
>
>
> Greets from Bavaria
>
> Freisei
>
> (Sorry for the topic-change, but i could no more read such a bad subject)
------------------------------
Message: 2
Date: Wed, 28 Jul 2021 10:13:40 -0500
From: Jeff Epler <jep...@unpythonic.net>
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Using `main` instead of `master` branch
Message-ID: <20210728151340.awmrcqkrqmh3i...@unpythonic.net>
Content-Type: text/plain; charset=us-ascii
On Tue, Jul 27, 2021 at 07:53:54PM +0000, Alec Ari via Emc-developers wrote:
> Hi everyone,
>
> Are there plans to switch the master branch to main? Just curious. I saw they
> changed it for the Mesa3D git repo and that's the default now for Github.
I'm not opposed to it. We'll want to make sure that buildbot
understands the change, and update documentation, so it's not something
that is without small cost; But before long I think people will be
surprised and confused by the old names, just as some people experience
surprise the first few times they ran into the new name for the default
branch.
(For my work we've converted hundreds of repos over, and had little
trouble from developers and a bit more trouble from scripts &
automation)
I will be happy to pitch in with the technical steps on github and
advise developers on what they need to do after the change.
Jeff
------------------------------
Message: 3
Date: Thu, 29 Jul 2021 02:29:00 +0100
From: andy pugh <bodge...@gmail.com>
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Using `main` instead of `master` branch
Message-ID:
<CAN1+YZUx-BQq=w3DSo23Wcq_Cmu3p2gQeJ5R=65aupq4is3...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Wed, 28 Jul 2021 at 16:14, Jeff Epler <jep...@unpythonic.net> wrote:
> I'm not opposed to it.
I object to objecting to "master". The word itself has so many
meanings unrelated to a particular period in the millenia through
which the slave trade existed.
My school had a headmaster. The UK judiciary has a "Master of the
Rolls". "Master" does not imply "and slave"[1]
I also object to "Main" as it isn't.
Neither name accurately describes the "development" branch.
Current "master" is in no sense the "master". Changes in "master" do
not propagate into the released branches.
I support changing the name to more accurately describe the branch as
the development branch, and propose "dev"
[1] As a small-case sub-note: This objection to "master" is US
cultural imperialism, based on _your_ history.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
? George Fitch, Atlanta Constitution Newspaper, 1912
------------------------------
Message: 4
Date: Thu, 29 Jul 2021 03:51:02 +0000 (UTC)
From: Alec Ari <neotheu...@ymail.com>
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Using `main` instead of `master` branch
Message-ID: <860258007.537879.1627530662...@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8
I'm fine with anything but `dev` is probably the best choice due to a better
representation of the purpose that branch serves. I fully agree.
Alec
On Thursday, July 29, 2021, 01:30:46 AM UTC, andy pugh <bodge...@gmail.com>
wrote:
I also object to "Main" as it isn't.
Neither name accurately describes the "development" branch.
Current "master" is in no sense the "master". Changes in "master" do
not propagate into the released branches.
I support changing the name to more accurately describe the branch as
the development branch, and propose "dev"
------------------------------
Message: 5
Date: Thu, 29 Jul 2021 04:19:19 +0000
From: Chris Morley <chrisinnana...@hotmail.com>
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Using `main` instead of `master` branch
Message-ID:
<mwhpr05mb364683c238ec21f8ae9857b2c0...@mwhpr05mb3646.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
________________________________
From: andy pugh <bodge...@gmail.com>
Sent: July 29, 2021 1:29 AM
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: Re: [Emc-developers] Using `main` instead of `master` branch
On Wed, 28 Jul 2021 at 16:14, Jeff Epler <jep...@unpythonic.net> wrote:
> I'm not opposed to it.
I object to objecting to "master". The word itself has so many
meanings unrelated to a particular period in the millenia through
which the slave trade existed.
My school had a headmaster. The UK judiciary has a "Master of the
Rolls". "Master" does not imply "and slave"[1]
I also object to "Main" as it isn't.
Neither name accurately describes the "development" branch.
Seems like another solution looking for a problem.
Do we really need to waste our time changing names and breaking things just to
pick another work that essentially means the same thing?
Let's not waste the little development energy we have.
Chris
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
------------------------------
End of Emc-developers Digest, Vol 183, Issue 30
***********************************************
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
