Hi Mark,

Sorry, I wasn't clear.  I don't know *nix OSes much, but under Windows 
(NTFS), we have 3 file time stamps for each file (Creation, Last Read and 
Last Write).  I think it would practical only to consider the last write 
time.

I don't see any technical reason for not having it other the software 
didn't bother to consider it perhaps, more complex to keep another data 
record/list/index around?  But Git for Windows certainly could easily 
supported it if the coder really wanted to do port it.

Anyway, I am thinking at looking at the source to fix the Git Daemon under 
Windows. I think it has a half close socket problem. Maybe I could look 
into adding a "--keeptimes" option.

---
HLS

On Monday, June 5, 2017 at 5:47:59 PM UTC-4, Mark Waite wrote:
>
> On Mon, Jun 5, 2017 at 3:31 PM <winser...@gmail.com <javascript:>> wrote:
>
>> Hi,  Is there an option or version of GIT with a database that keeps the 
>> last file stamp of committed files??   
>>
>>
> It depends what you mean by "file stamp".
>
> If "file stamp" means a cryptographically strong checksum of the contents 
> of the file, then yes, that is retained in all versions of git.
>
> If "file stamp" means the time of the most recent commit, then yes, the 
> time of the most recent commit is recorded in the commit log by all 
> versions of git.
>
> If "file stamp" means the names of the files included in the most recent 
> commit, then yes, that is recorded in the commit log by all versions of git.
>
> If "file stamp" means that files have their create date or modify date (or 
> other date related attribute) set to the date of the most recent commit on 
> checkout of that file, then no, that is not done in any version of git.  
> Refer to 
> https://stackoverflow.com/questions/2179722/checking-out-old-file-with-original-create-modified-timestamps
>  
> for more details.
>
> Mark Waite
>  
>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to git-users+...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to