I guess that's another reason why there's no desktop UI for fossil.
It's just that I prefer desktop apps to web apps generally, but I can
live with CLI + UI if there's nothing else.
This thread was not meant as criticism; It was just a question.
On 06/08/2018 03:18, Steve Landers wrote:
Put
On 6 Aug 2018, 9:19 AM +0800, Steve Landers , wrote:
> Put differently, what can’t you do with “fossil ui” that you can do with a
> native client?
>
> Drag and drop is the only one I can think of and I suspect that’s a good
> thing.
And also push notifications. While it can be done with web
On 2018-08-04 4:48 AM, Gilles wrote:
It might, since forum softwares (should) provide "sticky posts" that
are displayed at the top.
The one trick I've seen that seems most effective is to integrate the
search function with the New Topic function such that the user is
presented with a dynamic
On 8/6/18, joerg van den hoff wrote:
> this is a pure
> CLI/ssh scenario.
The ssh transport works by invoking the same HTTP processing engine as
is used on a website, just on the far end of an ssh tunnel. It's all
the same under the covers.
That said, I do remember making some minor changes to
On Aug 5, 2018, at 2:14 PM, Gilles wrote:
>
> 1. SQLite is a DLL + EXE package
A great many programs have need for an embedded DBMS. Very few programs have
need for an embedded DVCS.
Note also that these are empirical observations, rather than opinions.
> 2. There's no maintained GUI for
On Mon, Aug 6, 2018 at 8:07 AM
wrote:
>
> Date: Mon, 6 Aug 2018 09:18:56 +0800
> From: Steve Landers
> Subject: Re: [fossil-users] Why no EXE+DLL like SQLite?
>
> Put differently, what can’t you do with “fossil ui” that you can do with a
> native client?
>
You can't do:
fossil add
fossil ci
On 06.08.18 22:19, Richard Hipp wrote:
> Here is the technical problem I am having difficulty with. My
> currently solution is (probably) what is causing the delays and errors
> you are seeing. Suggestions from you are any mailing list reader on
> how to solve this problem are appreciated.
I've
On Aug 6, 2018, at 11:30 AM, Philip Bennefall wrote:
>
> a second commit right afterwards caused a segfault again
In advance of drh getting time to work on this, maybe you could give two
debugging steps on your end:
1. If you’re doing this on a platform that will run Valgrind, try running a
On Mon, Aug 6, 2018 at 12:57 PM
wrote:
> Date: Mon, 6 Aug 2018 11:18:09 -0500
> From: Artur Shepilko
> Subject: Re: [fossil-users] Why no EXE+DLL like SQLite?
> Message-ID:
>
> How would you want to use such a GUI?
> I mean practically what is a non-programmer user workflow that
> involves a
On 8/6/18, joerg van den hoff wrote:
> I see substantial delay (order of many seconds to minute(s)) when
> executing
>
> seen with 2.6 [74c908e709] 2018-08-03 21:06:57 UTC
>
Please try https://www.fossil-scm.org/fossil/info/71260ba25e79f4aa and
let me know whether or not that resolves the issue.
On 07/08/2018 03:21, Ron W wrote:
I never tried Sharp Fossil, but Fuel was a very clunky GUI. I think
non-programmers would be unwilling to put up with it.
As a simpler alternative, the "GUI" could just be implemented as an
extension to Windows Explorer, where users would just right-click a
I see substantial delay (order of many seconds to minute(s)) when
executing
`fossil sync' or `fossil uv sync'
between a clone and a "remote" repository residing on the same file system and communicating via
ssh. the command finally succeeds and completes (but it really takes time...)
On 8/6/18, Philip Bennefall wrote:
> But I wanted to report our experience in case it is of use to the
> developers, and in case doing so could give us some assistance with the
> immediate issue.
Thank you for the report. This is definitely something that should be
fixed. But I have a large
We have a repository in our organization which stores a number of rather
large binary files. When attempting to commit, we sometimes get
something like this:
ERROR: [largefile.bin is 999378424 bytes on disk but 210746789 in the
repository
The file in question was not modified during the
How would you want to use such a GUI?
I mean practically what is a non-programmer user workflow that
involves a VCS interaction via GUI?
The reason I ask, is that on several occasions I tried to convince
"ordinary" users to incorporate a VCS into their daily tasks. Not just
Fossil VCS, but Git
On 8/6/18, Philip Bennefall wrote:
> We have a repository in our organization which stores a number of rather
> large binary files. When attempting to commit, we sometimes get
> something like this:
>
>
> ERROR: [largefile.bin is 999378424 bytes on disk but 210746789 in the
> repository
My guess
On 8/6/18, Philip Bennefall wrote:
> Do you have any recommendations for something we could try in order to
> get more information, or would you suggest that we switch to another
> DVCS if we need to store files of these sizes?
Regardless of the problem, I don't think *any* DVCS is appropriate
OK. I'll investigate. Thanks for the quick response.
Kind regards,
Philip Bennefall
On 8/6/2018 6:50 PM, Richard Hipp wrote:
On 8/6/18, Philip Bennefall wrote:
Do you have any recommendations for something we could try in order to
get more information, or would you suggest that we switch
Do you have any recommendations for something we could try in order to
get more information, or would you suggest that we switch to another
DVCS if we need to store files of these sizes?
Kind regards,
Philip Bennefall
On 8/6/2018 6:33 PM, Richard Hipp wrote:
On 8/6/18, Philip Bennefall
On 8/6/18, Richard Hipp wrote:
> On 8/6/18, Philip Bennefall wrote:
>> Do you have any recommendations for something we could try in order to
>> get more information, or would you suggest that we switch to another
>> DVCS if we need to store files of these sizes?
>
> Regardless of the problem, I
Additional information: The repo checksum is disabled locally. When
enabling it, we get:
Segmentation fault: 11
Kind regards,
Philip Bennefall
On 8/6/2018 6:11 PM, Philip Bennefall wrote:
We have a repository in our organization which stores a number of
rather large binary files. When
The following command solved the issue at least for the moment:
fossil rebuild --vacuum --analyze --compress
I'm not yet sure which of the options made the difference, but I wanted
to report back nevertheless.
Kind regards,
Philip Bennefall
On 8/6/2018 6:57 PM, Philip Bennefall wrote:
OK.
22 matches
Mail list logo
