In this mailing list we need to know everything about fossil and fossil related
stuffs.- inetd/xinetd etc. that may be used in conjonction with Fossil (may be
I am the only one who hear about a daemon (inetd) that was used with Fossil?)
- security related (Fossil is a server sort of)-
Hi,
I would like to have some information, even little one about IDE that have
Fossil as a DVCS (even a plugin that is experimental).
a) glade/GTK based IDE Qt based
wxWidget based Python based Java based
etc.
b) it could be interesting if you could give your point of view about
Mr. User (if that is indeed your name):
On 10/26/2016 4:30 PM, K. Fossil user wrote:
In this mailing list we need to know everything about fossil and
fossil related stuffs.
- inetd/xinetd etc. that may be used in conjonction with Fossil (may
be I am the only one who hear about a daemon (inetd)
On Wed, Oct 26, 2016 at 1:02 AM, K. Fossil user
wrote:
> For example, today I've learned that Luca is not aware about security like
> 90% of Windows normal users...
And still you don't learn what to ask on the right mailing list.
Stop trolling.
Dear readers,
after a new release is the task 'fossil rebuild $existing_repro' a
SHOULD, a MUST or is it not necessary?
https://www.ietf.org/rfc/rfc2119.txt
Is there an internal trigger, if it should be necessary in future versions?
There were no technical problems and it is more of a kind of
On 10/26/16, Kain Abel wrote:
> Dear readers,
>
> after a new release is the task 'fossil rebuild $existing_repro' a
> SHOULD, a MUST or is it not necessary?
There have been no database schema changes, so a rebuild is not necessary.
You might want to run "fossil rebuild
Thanks for the quick clarification and the useful tips.
With regards,
Kain
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 26 October 2016 at 14:37, Karel Gardas wrote:
> Anyway, there is small nitpick. While using incremental import on such
> repo, fossil is horribly slow. The pstack command reveals that
> majority of time is spent in import_cmd -> export_marks ->
> mark_name_from_rid call
On 10/26/2016 05:37 PM, Karel Gardas wrote:
> I'm now able to import OpenBSD
> source tree from OpenBSD src git mirror to fossil.
This might be a silly question since I am terribly uniformed of the
issues but could you have imported the OpenBSD source directly from
their CVS repository?
A quick follow-up. A few folks asked if the Fossil plugin for Qt Creator
supports "Commit" action -- it does support commit.
I missed to list it in my original email, sorry for the confusion.
This is actually mentioned on the project page:
https://github.com/nomadbyte/qtcreator-plugin-fossil
At a
Hello,
first of all thanks a lot to the developer(s) who fixed import and
incremental import from git to fossil. I'm now able to import OpenBSD
source tree from OpenBSD src git mirror to fossil.
Anyway, there is small nitpick. While using incremental import on such
repo, fossil is horribly slow.
On Wed, Oct 26, 2016 at 11:53 PM, Adam Jensen wrote:
> On 10/26/2016 05:37 PM, Karel Gardas wrote:
>> I'm now able to import OpenBSD
>> source tree from OpenBSD src git mirror to fossil.
>
> This might be a silly question since I am terribly uniformed of the
> issues but could
On Wed, Oct 26, 2016 at 11:44 PM, jungle Boogie wrote:
> On 26 October 2016 at 14:37, Karel Gardas wrote:
>> Anyway, there is small nitpick. While using incremental import on such
>> repo, fossil is horribly slow. The pstack command reveals that
>>
13 matches
Mail list logo