On 08/06/2016 23:51, Sebastian Huber wrote:
Given the file name rtems-gcc-4.9.3-newlib-2.4.0-1.cf, how does this fit
to the new file content? We have this *-N.cfg pattern throughout. What
is the rule for the N? Is it useful at all?
This was present when we had no branching in the repo to help m
On 08/06/16 00:49, Hesham Almatary wrote:
---
rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg
b/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg
index 596a4
Hi Hesham,
Looks fine to commit. Do you have commit write access?
Chris
On 8/06/2016 8:49 AM, Hesham Almatary wrote:
---
rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.
---
rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg
b/rtems/config/tools/rtems-gcc-4.9.3-newlib-2.4.0-1.cfg
index 596a4a7..42f6cfa 100644
--- a/rtems/config/tools/rt