Actually it's not clear what revert does. I removed the file and revert didn't recover it. I created an empty file and revert didn't recover it. (But maybe this is timestamp related, or because I'm on the machine that created the uv file in the first place.)
Thanks ../Dave On 14 June 2017 at 01:41, David Mason <[email protected]> wrote: > `fossil uv list` doesn't mention any path information. Does it have path > information behind the scenes so that `fossil uv revert` can put the file > in the original place? > > Is there a way to find if any unversioned file has been updated apart from > looking at the hash or the date for particular files? > > Thanks ../Dave > > On 14 June 2017 at 01:32, David Mason <[email protected]> wrote: > >> I finally got around to this, but I got the following errors on Linux: >> : ~/Sites/p4ru/kitPJS ; fossil unversioned revert >> Usage: fossil sync URL >> : ~/Sites/p4ru/kitPJS ; fossil ver >> This is fossil version 2.2 [81d7d3f43e] 2017-04-11 20:54:55 UTC >> : ~/Sites/p4ru/kitPJS ; fossil unversioned list >> 504e6cf08911 2017-06-14 00:45:18 378207 60173 index.js >> : ~/Sites/p4ru/kitPJS ; fossil sync -u >> Usage: fossil sync URL >> : ~/Sites/p4ru/kitPJS ; fossil unver cat index.js|wc >> 2234 7960 378207 >> >> I downloaded this version today from the website. On MacOSX, `fossil sync >> -u` seems to work fine (as does `fossil unver revert`). It's good that cat >> works, but revert seems nicer! >> >> Thanks ../Dave >> >> On 10 May 2017 at 09:34, David Mason <[email protected]> wrote: >> >>> Perfect! I knew it would be easy. >>> >>> Thanks >>> >>> On 10 May 2017 at 07:04, Richard Hipp <[email protected]> wrote: >>> >>>> On 5/10/17, David Mason <[email protected]> wrote: >>>> > I have a fossil repo and in it I have a file foo.js that is generated >>>> by my >>>> > build process - so I don't want it versioned. But I *do* want it >>>> > distributed, and want it referencable from foo.html - which *is* >>>> versioned. >>>> > foo.html and foo.js are *not* served by fossil, but by a simple >>>> apache or >>>> > nginx server. >>>> > >>>> > So in my working directory I create foo.js and then do what to get it >>>> moved >>>> > to the master fossil repo. >>>> >>>> fossil uv add foo.js >>>> fossil uv sync >>>> >>>> >>>> > Then on my production machine I do what command >>>> > to get the current version of foo.js from the master fossil repo? >>>> >>>> fossil uv sync >>>> fossil uv export foo.js foo.js >>>> OR: fossil uv cat foo.js >foo.js >>>> >>>> > >>>> > I'm sure it's easy, but the documentation does not give me guidance >>>> on this >>>> > simple use-case. >>>> > >>>> > Thanks ../Dave >>>> > >>>> >>>> >>>> -- >>>> D. Richard Hipp >>>> [email protected] >>>> _______________________________________________ >>>> fossil-users mailing list >>>> [email protected] >>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>>> >>> >>> >> >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
