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:
`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?
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
504e6cf0
Great, I'll give that a try.
On Wed, May 10, 2017 at 4:17 PM, Richard Hipp wrote:
> On 5/10/17, sky5w...@gmail.com wrote:
> > Cool,
> > Does this behave identically if I have:
> > http://localhost:8082/setup_settings
> > [±] autosync //<-- ON or OFF?
> >
>
> Yes. Unversioned content does
On 5/10/17, sky5w...@gmail.com wrote:
> Cool,
> Does this behave identically if I have:
> http://localhost:8082/setup_settings
> [±] autosync //<-- ON or OFF?
>
Yes. Unversioned content does not autosync. You have to explicitly
runt "fossil uv sync".
--
D. Richard Hipp
d...@sqlite.org
Cool,
Does this behave identically if I have:
http://localhost:8082/setup_settings
[±] autosync //<-- ON or OFF?
Thanks.
On Wed, May 10, 2017 at 9:34 AM, David Mason wrote:
> Perfect! I knew it would be easy.
>
> Thanks
>
> On 10 May 2017 at 07:04, Richard Hipp wrote:
>
>> On 5/10/17, Da
Perfect! I knew it would be easy.
Thanks
On 10 May 2017 at 07:04, Richard Hipp wrote:
> On 5/10/17, David Mason 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 wan
On 5/10/17, David Mason 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 fo
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 se
9 matches
Mail list logo