Hello Samuel,
First, never use Windows date/time as reference, it is just a view of
your local repo and there no link with git information.
> In GIT, as shown above, all dates of *.sci are actually very recent.
Not really, in fact image/view of the repo on your system have recent
dates. Windows file system dates can change on clone, pull/rebase,
checkout...
for example:
$ ls -lA savematfile.sci
-rw-r--r-- 1 tonio 197121 16480 *oct. 25 2017* savematfile.sci
$ touch savematfile.sci && ls -lA savematfile.sci
-rw-r--r-- 1 tonio 197121 16480 *nov. 17 15:35* savematfile.sci
But for git the file is not modified.
Regards,
Antoine
Le 17/11/2018 à 14:01, Samuel Gougeon a écrit :
Dear devs,
In order to understand how the bug 15877
<http://bugzilla.scilab.org/show_bug.cgi?id=15877> has recently
appeared and why this patch <https://codereview.scilab.org/20514> has
recently regressed,
i was looking at the modifications dates of files in SCI/matio/macros
in GIT - branch 6.0
and was comparing them with histories of files as available on
http://gitweb.scilab.org
In GIT, as shown above, all dates of *.sci are actually very recent.
However, last changes reported by gitweb histories are all in 2017,
for instance
Knowing that the last 6.0=> master merge was done on 2018-10-22
<https://codereview.scilab.org/#/c/20575/>, so after
the 2018-09-23 modification done on savematfile.sci as reported on GIT,
how is this possible?
From where these discrepancies come from?
What is reliable for the code follow-up?
Thanks
Best regards
Samuel
_______________________________________________
dev mailing list
dev@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/dev
