Re: [fossil-users] Can Fossil preserve file timestamps when opening a repository ?
On 4/19/17, Martin Irvinewrote: > I would prefer that Fossil preserved the date and time stamp that the file > had when it was most recently committed. > That is an unusual preference, because most people when they do fossil update some-older-verion expect afterwards to be able to type "make" in order to build that older version, but if the timestamps are some point in the past, then that make will not work. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Can Fossil preserve file timestamps when opening a repository ?
It has been discuss a few times before. I think here is a good summary about why it is like this now: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg15013.html -- Martin G. Le mer. 19 avr. 2017 à 19:41, Martin Irvinea écrit : > Hi, > > This seems a pretty basic question but I can't seem to find an answer or > explanation online... > > I am a fairly new Fossil user and I am surprised that when I open a > repositiory (on Windows 7) all the extracted files seem to have their > timestamp set to the date and time at which they were extracted (that is, > the date and time at which I opened the repository). > > I would prefer that Fossil preserved the date and time stamp that the file > had when it was most recently committed. > > In fact, it seems to me this resetting of the timestamps is a bad idea, > unless someone can explain to me why this is a good idea ? > > More importantly, unless it really is a good idea that it doesn't, is > there a way I can get Fossil to preserve the date and time stamps on the > files it extracts from a repository ? > > > I would appreciate any thoughts, clarification or guidance on this. > > > > Thanking you for your assistance, > > > > > > Martin Irvine. > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Can Fossil preserve file timestamps when opening a repository ?
Hi, This seems a pretty basic question but I can't seem to find an answer or explanation online... I am a fairly new Fossil user and I am surprised that when I open a repositiory (on Windows 7) all the extracted files seem to have their timestamp set to the date and time at which they were extracted (that is, the date and time at which I opened the repository). I would prefer that Fossil preserved the date and time stamp that the file had when it was most recently committed. In fact, it seems to me this resetting of the timestamps is a bad idea, unless someone can explain to me why this is a good idea ? More importantly, unless it really is a good idea that it doesn't, is there a way I can get Fossil to preserve the date and time stamps on the files it extracts from a repository ? I would appreciate any thoughts, clarification or guidance on this. Thanking you for your assistance, Martin Irvine. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Incomplete patch with idea for enhancement
On Wed, Apr 19, 2017 at 8:00 AM,wrote: > > Date: Tue, 18 Apr 2017 23:52:33 -0600 > From: Warren Young > Subject: Re: [fossil-users] Incomplete patch with idea for enhancement > > The only open question in my mind is what to do on Windows? IIS must have > such a DB, but how does a program access it? > In MS Windows, that DB is the Windows Registry - along with a huge amount of other stuff. I've never written a program specifically for MS Windows, so I don't know what's involved. However, I have used the Nullsoft Scripable Installer System to make installers for Ms Windows for some of my programs and it has the ability to query (and modify) the registry, so there is a way to access the information in it. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Incomplete patch with idea for enhancement
On 4/19/2017 12:52 AM, Warren Young wrote: I’d call your patch “close enough.” It’s only got a 1 in 4 billion chance of matching something incorrectly for a uniform probability distribution, and a much smaller chance than that in practice given the bias towards text file types in Fossil repositories. My idea was to have a way to specify the mime type on a per-file basis. Or maybe by file extension like the 'encoding-glob', etc. settings? So far, the one-off policy works pretty well, since typical web browsers don’t add new internally-viewable file types that often. With this move away from plugins, the list of viewable file types may be *shrinking* at the moment. I’m not rejecting the idea, I’m just calling into question its ROI. My thinking went like this: + showing a PNG is neat + why doesn't it show an ICO? + make a quick little patch so it does + the patch is not 100% certain to ID an ICO + how to make it 100%? + a) allow one to set mime on a per-file basis -- advantage: 100% reliable -- disadvantage: has to be done for each applicable file + b) use file suffix -- advantage: applies gobaly -- disadvantage: applies globally & is prob. a lot more work Since I know nothing about the internal workings of fossil, I have no way to judge how much effort it would be. The bottom line: this is just cosmetic so it's probably not worth spending much effort on it. Maybe, as you mentioned, the simple patch could be added since it would work most of the time. In addition, even if it erred, browsers just show a broken image for an file that fails to decode. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users