On Fri, Oct 10, 2014 at 1:56 PM, Graeme Pietersz <gra...@pietersz.net> wrote:
> Thanks for the explanation, further questions below if I can stretch > your patience a bit! > Not stretching at all, except that i'm trying to stretch my imagination as to how fossil might be used to do this ;). Test and production are on the same server so I had intended them to > use the same repo file. In that case I would not have that problem? > If your production copy also opens the repo one time, all you have to do to update it is "fossil update", and (A) all newer files will be updated (with new timestamps), (B) unchanged files will be left unchanged, and (C) files of your own will not be touched. > > Can you not make the production copy a checkout of a production-local > repo? > > I plan to do this if you tell me the latest iteration of the above will > not work :) i can't think of another way to get what you want which is doable using existing features. > I was trying to preserve timestamps. I think I can work > around that without much harm. > If your prod copy simply opens and updates from the same repo file as the test copy, you won't have any unusual problems with timestamps. They will get set once during open, and then updated as changes arrive for each file. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
