On Dec 18, 2017, at 8:22 PM, jungle boogie wrote:
>
> I can't remember the repo drh mentioned
TH3, the paid-for test harness for SQLite:
https://sqlite.org/th3.html
> So if you committed something as drh with an improved overview section
> showing gpg keys, would this has prevented confusi
On Mon, Dec 18, 2017 at 9:30 PM, jungle boogie
wrote:
> Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500
>
>> You can now see the canonical Fossil self-hosting repository using any
>> of the built-in skins by visiting links from this page:
>> https://www.fossil-scm.org/skins/
>>
>
> Than
Thus said Richard Kipp on Sun, 17 Dec 2017 21:11:30 -0500
You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/
Thanks for the link, this is a very handy way to see all the skins.
This is
Thus said Warren Young on Mon, 18 Dec 2017 17:55:16 -0700
I want to restrict this thread to the technical issues: preventing
wyoung/tangent confusions, or helping Donny trust Alice, or or giving Donny the
tools to *not* trust Alice just because Bob trusts Alice.
I can't remember the repo drh
On Dec 18, 2017, at 5:55 PM, Warren Young wrote:
>
> Git does it by using email addresses for identity instead of user names
It also occurs to me that Git typically inverts the push/pull relationship as
compared to Fossil. I can’t get random checkins into Linus’ git tree merely
because one of
On Dec 18, 2017, at 7:04 PM, bch wrote:
>
> Does contemporary Linux not randomize its PIDs?
It may be an option, but it isn’t happening on a near-stock CentOS 7 box I have
near at hand here:
$ ls > /dev/null & echo $!
Run that repeatedly on a quiet system, and chances are, you’ll get ste
On Mon, Nov 6, 2017 at 9:19 AM Warren Young wrote:
> On Nov 3, 2017, at 12:08 PM, Richard Hipp wrote:
> >
> > On 11/3/17, Olivier R. wrote:
> >>
> >>
> >> Sorry. My knowledge of the C toolchain is null.
> >
> > The next step will be to figure out
> > how to attach the debugger to a hung process
Came back to this after dinner.
The introduction of new Timeline classes(Modern,Compact,Verbose,Columnar)
means there is no catch-all for timelineComment.
So, I cut and paste in the CSS for each possible case.
/* Enable timeline comments to respect linefeeds. */
span.timelineModernComment {
font-
On Dec 18, 2017, at 6:52 AM, Olivier R. wrote:
>
> When gdb was active, Fossil didn’t answer when asking for a webpage. It
> seemed blocked.
That’s exactly what happens. If you want the process to run while GDB remains
attached, say “cont” after attaching.
> Here is what gdb said:
Did it sa
On Dec 17, 2017, at 1:44 PM, Kevin wrote:
>
> I believe deception and impersonation are important.
I agree. One of the core tenets of Fossil is durable accountability, and here
we have a case where it allows the who-did-what history to be muddied.
What Fossil allowed in the case that started
Why not support --dryrun and --dry-run but only document the former? Then
scripts won't break. It's not like anyone is going to accidentally use
--dry-run to mean something else.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
Ok, I clicked and clacked with the Publish button and I am getting changes.
Before, I could edit my CSS and the page would reflect the changes
immediately.
I now think I have a corrupt CSS, since I lost my menus and header/footer.
I'll edit the default CSS and re-insert the 'white-space: pre;' item
>From my previous CSS:
/* Enable Check-in comments to respect linefeeds. */
span.checkinComment {
font-family: Consolas;
white-space: pre;
}
/* Enable timeline comments to respect linefeeds. */
span.timelineComment {
font-family: Consolas;
white-space: pre;
}
/* This was mentioned in the ma
Thus said sky5w...@gmail.com on Mon, 18 Dec 2017 11:17:49 -0500:
> I just compiled fossil version 2.5 [a6c5a4620a] 2017-12-18 02:06:40
> UTC under Windows 10 and nothing(every view option + CSS + Timeline
> option) I try shows my commit comment[CR][LF]'s.
What CSS and Timeline option are yo
I just compiled fossil version 2.5 [a6c5a4620a] 2017-12-18 02:06:40 UTC
under Windows 10 and nothing(every view option + CSS + Timeline option) I
try shows my commit comment[CR][LF]'s.
Any ideas?
My check-in comments are intentionally multi-line. Stripping the newlines
renders my timeline as noise.
OK. It happened again while I was away for few days.
The main process has created 10 subprocesses. Fossil was very slow.
I used gdb on the main process.
When gdb was active, Fossil didn’t answer when asking for a webpage. It
seemed blocked. And Fossil was responsive again few seconds after I q
At the time of this writing, the "timeline-commit-format" option seems
"orphaned", i.e. it is only referenced by the /setup_timeline web page
to display the setting, but not queried or honored any more.
As the timeline web view mode defines the display format, I'd like to
suggest to change this op
Following patch fixes the clash of the short forms of the --limit and
--dryrun options for the `fossil tag' command.
Another form than -N|--limit might be preferred to ensure a better
distinction from -n|--dryrun, such as -c|--limit or -l|limit.
--Florian
Index: src/tag.c
===
Following patch changes all --dryrun options to the more common form
--dry-run for all commands, but this would break working scripts!
--Florian
Index: src/tag.c
==
--- src/tag.c
+++ src/tag.c
@@ -282,11 +282,11 @@
}
/*
** OR thi
Fwiw, i agree completely, plus suspect (without knowing for certain) that
including a user's IP (and thus, indirectly, location) in the permanent
record _might_ run afoul of privacy laws in some jurisdictions.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos
2017-12-18 5:58 GMT+01:00 Ron W:
> All I'm suggesting is that the information already being put in the
> "rcvfrom" table (that DRH mentioned) also be saved as tags to the commits
> they refer to. Therefore, the tags will have the same meaning as the entries
> in the existing "rcvfrom" table.
Well,
21 matches
Mail list logo
