eduardo at monkey.io
Wed May 27 21:09:37 UTC 2015
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 Sherrill <joel.sherrill at oarcorp.com>
> 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
> This is on imported source in a repo that has been converted from
> cvs to git. In the process, the timestamp on the autotools
> generated files got broken. I can touch them and all is good
> but git doesn't see that as a change.
>> On Sat, May 23, 2015 at 9:08 AM, Joel Sherrill
>> <joel.sherrill at oarcorp.com <mailto:joel.sherrill at oarcorp.com>> wrote:
>> 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.
>> devel mailing list
>> devel at rtems.org <mailto:devel at rtems.org>
>> Eduardo Silva
>> Monkey Software
> Joel Sherrill, Ph.D. Director of Research & Development
> joel.sherrill at OARcorp.com On-Line Applications Research
> Ask me about RTEMS: a free RTOS Huntsville AL 35805
> Support Available (256) 722-9985
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel