On 06/06/2019 09:09, Chris Johns wrote:
I am fine with the git hash being present. It does make it easy find the history
given a tarball.
You asked for a timeline. Even with
rtems-gcc-7-fb371a33fa6-newlib-5c2a3661c
rtems-gcc-7-32fc1a32aa6-newlib-5c2a3661c
you don't know which GCC 7 branch comm
On 6/6/19 5:01 pm, Sebastian Huber wrote:
> On 06/06/2019 08:05, Chris Johns wrote:
>> On 6/6/19 3:04 pm, Sebastian Huber wrote:
>>> On 06/06/2019 02:23, Chris Johns wrote:
On 5/6/19 10:16 pm, Sebastian Huber wrote:
> +tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
Is there a timetable
On 06/06/2019 08:05, Chris Johns wrote:
On 6/6/19 3:04 pm, Sebastian Huber wrote:
On 06/06/2019 02:23, Chris Johns wrote:
On 5/6/19 10:16 pm, Sebastian Huber wrote:
+tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
Is there a timetable for gcc 7 branch releases? I see the built gcc executable
cle
On 6/6/19 3:04 pm, Sebastian Huber wrote:
> On 06/06/2019 02:23, Chris Johns wrote:
>> On 5/6/19 10:16 pm, Sebastian Huber wrote:
>>> +tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
>> Is there a timetable for gcc 7 branch releases? I see the built gcc
>> executable
>> clearly shows the version of g
On 06/06/2019 02:23, Chris Johns wrote:
On 5/6/19 10:16 pm, Sebastian Huber wrote:
+tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
Is there a timetable for gcc 7 branch releases? I see the built gcc executable
clearly shows the version of gcc is 7.4.1 which is great so I am wondering if
this file
On 5/6/19 10:16 pm, Sebastian Huber wrote:
> +tools/rtems-gcc-fb371a33fa6-newlib-5c2a3661c
Is there a timetable for gcc 7 branch releases? I see the built gcc executable
clearly shows the version of gcc is 7.4.1 which is great so I am wondering if
this file name would be clearer if the branch was
