On 9/21/16, Steven Gawroriski wrote:
>
> If a file is in the unversioned space _and_ the in the actual
> repository, is the data deduplicated between them?
No. Not at this time.
That seems an unlikely scenario. Logic could be added to deduplicate,
but that would merely be an optimization - eve
On Mon, 19 Sep 2016 15:37:05 -0400
Steven Gawroriski wrote:
> On Mon, 19 Sep 2016 14:49:43 -0400
> Richard Hipp wrote:
>
> > On 9/19/16, Steven Gawroriski wrote:
> > >
> > > I get the following assertion error:
> > >
> > > fossil: ./src/xfer.c:1893: client_sync: Assertion `uvStatus==2'
> > > f
On Mon, 19 Sep 2016 14:49:43 -0400
Richard Hipp wrote:
> On 9/19/16, Steven Gawroriski wrote:
> >
> > I get the following assertion error:
> >
> > fossil: ./src/xfer.c:1893: client_sync: Assertion `uvStatus==2'
> > failed. Aborted
> >
>
> The uvStatus various was once used for something, though
On 9/19/16, Steven Gawroriski wrote:
>
> I get the following assertion error:
>
> fossil: ./src/xfer.c:1893: client_sync: Assertion `uvStatus==2' failed.
> Aborted
>
The uvStatus various was once used for something, though I don't
remember what. It is unused now. So I simply removed it.
Let me
Hello,
I have checked out the latest revision and now `clone -u` works as
intended, very nice.
Another thing I have noticed is that for me, the unversioned revert
does not work if one is not authorized to push to the remote repository.
I have done the following:
$ fossil clone -u http://
Replyng to myself:
I have also noticed that `fossil clone -u` currently appears to have no
effect. When I clone from a remote repository with that switch no
unversioned files appear in my local repository.
___
fossil-dev mailing list
fossil-dev@mailingli
Some things I have noticed when it comes to the unversioned
feature:
* Upgrading from earlier versions to new versions, if the
"unversion" command has never been run then the web interface
shows a SQL error about a missing table. However, running the
command once even when there is nothi
