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
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
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
On Sat, May 23, 2015 at 9:08 AM, Joel Sherrill
wr
Hi
Working through the rtems-addon-packages, I have noticed
that the git conversion messed up the timestamps on some
files. It wants to run autoconf to regenerate them and doesn't
need to.
I did a find and touch locally but am not sure how to make
that show up in git.
Suggestions?
--joel
_
