On 28/05/2015 12:25 am, Joel Sherrill wrote:
>
>
> On 5/27/2015 9:06 AM, Gedare Bloom wrote:
>> I want to clarify what repos need to be synchronized (or eventually
>> tagged) with an RTEMS release. Currently we know (from [1]) the
>> following must:
>> rtems
>> examples-v2
>> network-demos
>> rte
On 5/27/2015 4:09 PM, Eduardo Silva wrote:
GIT basically will not recognize any change, because at "file content
level" there is no change, the SHA1 becomes the same.
That's what I suspected and that's right. Except git does also track
permissions. timestamp is usually bogus to store.
note:
GIT basically will not recognize any change, because at "file content
level" there is no change, the SHA1 becomes the same.
note: looks like auto-generated files should not be tracked, you can add
them to .gitignore and force the user to regenerate them.
On Wed, May 27, 2015 at 2:59 PM, Joel She
---
led/led.h | 23 +++
1 file changed, 23 insertions(+)
diff --git a/led/led.h b/led/led.h
index 3fee684..d22beda 100644
--- a/led/led.h
+++ b/led/led.h
@@ -80,6 +80,29 @@ uint8_t MPC8313_LED_Count;
#define LED_ON() do { unsigned int *gpio = (unsigned int
*)BCM2835_GPIO_
On 5/23/2015 11:36 AM, Eduardo Silva wrote:
Not sure about the purpose/need of that but for anyone cloning your
repo, the timestamps will be updated to the time those files are being
created locally.
On git is important the commits that affected a given file, e.g: git log
src/some_file.c
Th
On 5/27/2015 9:06 AM, Gedare Bloom wrote:
I want to clarify what repos need to be synchronized (or eventually
tagged) with an RTEMS release. Currently we know (from [1]) the
following must:
rtems
examples-v2
network-demos
rtems-testing
rtems-tools
rtems-source-builder
We don't know about:
rtem
I want to clarify what repos need to be synchronized (or eventually
tagged) with an RTEMS release. Currently we know (from [1]) the
following must:
rtems
examples-v2
network-demos
rtems-testing
rtems-tools
rtems-source-builder
We don't know about:
rtems-libbsd
rtems-addon-packages
rtems-graphics-t
