On 8/1/23 16:12, Joel Sherrill wrote:
Yes, go ahead.
Thanks,
But would it be more useful it the report included a hash?
Of course, but this is single-liner right?
Depending on what you like:
- git log -n 1
- git log -n 1|grep "^commit"|cut -d ' ' -f 2-
Karel
On Tue, Aug 1, 2023 at 9:0
Yes, go ahead.
But would it be more useful it the report included a hash?
On Tue, Aug 1, 2023 at 9:00 AM Karel Gardas wrote:
>
>Joel,
>
> not sure about what do you mean by "before the fix was pushed", but
> certainly RTEMS HEAD does not contain the fix for this yet and fix is
> already awa
Joel,
not sure about what do you mean by "before the fix was pushed", but
certainly RTEMS HEAD does not contain the fix for this yet and fix is
already awaiting review here:
https://lists.rtems.org/pipermail/devel/2023-July/076043.html
If you ok that, I may push...
Thanks,
Karel
On 8/1
I think this started before the fix was pushed but since there is no hash
in this report, it is impossible to be sure.
Since it already has to know about the rtems source tree, could it include
a hash? How hard is that to implement?
--joel
-- Forwarded message -
From: OAR Tester f
