Modification dates mismatch between GIT and gitweb

classic Classic list List threaded Threaded
3 messages Options
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Modification dates mismatch between GIT and gitweb

Dear devs,

In order to understand how the bug 15877 has recently appeared and why this patch 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, 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
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev
Antoine ELIAS-2 Antoine ELIAS-2
Reply | Threaded
Open this post in threaded view
|

Re: Modification dates mismatch between GIT and gitweb

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 has recently appeared and why this patch 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, 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
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev


_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev
Samuel GOUGEON Samuel GOUGEON
Reply | Threaded
Open this post in threaded view
|

Re: Modification dates mismatch between GIT and gitweb

Hello Antoine,

Thanks for your answer:

Le 17/11/2018 à 15:40, Antoine ELIAS a écrit :
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...

Windows dates have been got just after a git checkout origin/6.0 + git fetch + git reset --hard origin/6.0.
As fas as i understand, this is supposed to refresh all local files and synchronize them with the remote GIT.
In addition, if dates were the one when files are copied to the local repo, they would all be the
same, after this "refreshing" sequence. This is not the case.

So, it is still unclear to me.

I will have a look on how GIT manages files with reset --hard.

Regards
Samuel

_______________________________________________
dev mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/dev