On 06/02/2020 00:11, Chris Johns wrote:
On 6/2/20 10:00 am, Amar Takhar wrote:
On 2020-02-06 08:31 +1100, Chris Johns wrote:
Can we enable this for one BSP from each tier 1 architectures?
Yes, can you provide a list?
The master list is here ...
https://git.rtems.org/rtems-tools/tree/config
On 2020-02-07 16:17 +1100, Chris Johns wrote:
>
> Could we build an "always must build" BSP and if it builds a wider selection
> are
> built? The beaglebone black is my pick.
That's the way it already works now and has for years.
Look at the waterfall the process is:
1. Build snapshot
2. B
On 7/2/20 4:05 pm, Amar Takhar wrote:
> On 2020-02-06 08:03 -0700, Gedare Bloom wrote:
>> I agree with what you say. (And appreciate the unfunded work.)
>> So, if this "Responsible User" email policy goes into effect, we also
>> need some additional policies for developers to help prevent the
>> "R
On 2020-02-06 08:03 -0700, Gedare Bloom wrote:
> I agree with what you say. (And appreciate the unfunded work.)
Thank you.
> I still have reservations about the possibility to generate 250 emails
> all basically the same. Perhaps developers/committers should test
> every commit. Sometimes though
On 2020-02-06 07:44 +0100, Christian Mauderer wrote:
> Like already said: I'm not against sending the mails. And the situation
> is quite unlikely in RTEMS core. But we should be aware of the
> possibility before enabling such an option.
Agreed and thank you for highlighting this. While I am sur
Thanks.
On Thu, Feb 6, 2020, 11:16 AM Ayush Dwivedi <21cencturyay...@gmail.com>
wrote:
> ---
> testsuites/ada/sptests/sp19/Makefile | 2 --
> testsuites/samples/hello/init.c | 2 +-
> 2 files changed, 1 insertion(+), 3 deletions(-)
> delete mode 100644 testsuites/ada/sptests/sp19/Makefile
---
testsuites/ada/sptests/sp19/Makefile | 2 --
testsuites/samples/hello/init.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
delete mode 100644 testsuites/ada/sptests/sp19/Makefile
diff --git a/testsuites/ada/sptests/sp19/Makefile
b/testsuites/ada/sptests/sp19/Makefile
deleted
Hello Ayush,
On Thu, Feb 6, 2020 at 3:51 AM Vaibhav Gupta wrote:
>
>
>
> On Thu, Feb 6, 2020, 4:15 PM Ayush Dwivedi <21cencturyay...@gmail.com> wrote:
>>
>> Hello everyone,
>>
>> I am new to RTEMS community. I wish to contribute to the RTEMS project. I
>> read on the RTEMS gsoc getting started p
On Thu, Feb 6, 2020 at 8:20 AM Sebastian Huber
wrote:
>
> On 06/02/2020 16:03, Gedare Bloom wrote:
>
> > So, if this "Responsible User" email policy goes into effect, we also
> > need some additional policies for developers to help prevent the
> > "RTEMS Horde of Broken Builds" (TM) emails especia
On 06/02/2020 16:03, Gedare Bloom wrote:
So, if this "Responsible User" email policy goes into effect, we also
need some additional policies for developers to help prevent the
"RTEMS Horde of Broken Builds" (TM) emails especially from going
outside of the core developers who at least might expec
On Thu, Feb 6, 2020 at 12:22 AM Chris Johns wrote:
>
> On 2020-02-06 17:15, Sebastian Huber wrote:
> > On 05/02/2020 22:13, Chris Johns wrote:
> >>
> >> After all one of roles of the RTEMS Foundation is education.
> >
> > I added a ticket for this:
> >
> > https://devel.rtems.org/ticket/3867
> >
>
On Wed, Feb 5, 2020 at 10:31 PM Amar Takhar wrote:
>
> On 2020-02-05 20:28 -0700, Gedare Bloom wrote:
> > I would like it to be a single email to indicate there is a new
> > breakage. Enough to indicate "hey go take a look at the full build
> > results! something is wrong here"
>
> That's what it
On Tue, 4 Feb 2020 at 13:28, Vijay Kumar Banerjee
wrote:
>
>
> On Tue, Feb 4, 2020, 11:33 AM Bran S wrote:
>
>> On Saturday, 1 February 2020, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>> >
>> >
>> >
>> > On Sat, Feb 1, 2020 at 9:31 PM Bran S wrote:
>> >>
>> >> On Sat, 1 Feb 202
On Thu, Feb 6, 2020, 4:15 PM Ayush Dwivedi <21cencturyay...@gmail.com>
wrote:
> Hello everyone,
>
> I am new to RTEMS community. I wish to contribute to the RTEMS project. I
> read on the RTEMS gsoc getting started page that I am required to submit a
> proof that I can contribute. Modifying the sa
Hello everyone,
I am new to RTEMS community. I wish to contribute to the RTEMS project. I
read on the RTEMS gsoc getting started page that I am required to submit a
proof that I can contribute. Modifying the sample executable hello.exe
source code along with the screenshot of it being tested on gd
Hello Chris,
please let me pick up the discussion again so that we manage to come
to a conclusion. Like Matthias said oflist, we are trying to address
the problem of the missing project overview in a separate thread. But
it would be really relevant to get a result for the python topics.
Again: In
16 matches
Mail list logo
