On Fri, Oct 10, 2014 at 11:01 AM, Graeme Pietersz <gra...@pietersz.net> wrote:
> I have another idea. Fossil diff and commit appear to ignore > file timestamps, so I think this will work: > > 1) Copy .fslckout from test to production. > 2) Update the path to the repo (which is probably the same as they both > have the same relative path to the repo). > 3) Run fossil diff to see which files have "changed", and manually > copy new versions over (there are only a handful). > Does that sound sane? > No, because the record IDs used in .fslckout are not guaranteed to refer to the same artifacts on the other side. .fslckout holds low-level blob IDs (instead of UUIDs) which refer to repo-side data in the local repo copy, and those IDs are not guaranteed to align 100% across any two clones of a given repo. That is not what I want to do: I want to turn a non-checkout dir > into a checkout dir without changing timestamps. > i can't currently conceive of a way to do that using fossil which provides the mix you're looking for. (fossil open) sets all files to the current timestamp, so by itself that won't work. The --keep option would keep any old timestamps, but it would not touch _any_ pre-existing files, so i can't imagine that being terribly useful for you (it won't update anything more often than not). Can you not make the production copy a checkout of a production-local repo? -- ----- 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
