On 06/24/18 05:27, j. van den hoff wrote:
additionally, mabye shorten the footer separation line to exactly two
`--', treating the footer as the sender's "affiliation/identity" (which
usually leads to a less prominent display by the email client).
If you're talking about email signatures, they
On Sun, Jun 24, 2018 at 11:19 PM David Mason wrote:
> I really don't understand the reticence to use setjmp/longjmp to turn all
> of these short-cut exits into library return-to-API trampolines. It
>
To be clear: that's my reticence, not Richard's. libfossil was always
effectively a third-party
I really don't understand the reticence to use setjmp/longjmp to turn all
of these short-cut exits into library return-to-API trampolines. It would
allow you to retain all the existing fossil codebase. Rewriting the code
into library form is an interesting project, but it seems like a huge
amount
> On 6/23/18, Jungle Boogie wrote:
> >
> > no such table: subscriber SELECT 1 FROM subscriber WHERE suname='jungle'
>
> The email notification tables are created on-demand. Apparently I
> have missed a call to "email_schema()" someplace in the code. Fix
> this by running the command:
>
>
Attached a zip file containing a number of mails as generated and send
by `fx` (https://core.tcl.tk/akupries/fx/index) to the tcl-bugs mailing
list. Soory, it was easiest to pull existing mails.
The footer ("See Tcl/Tk ...") is configurable.
The general structure is currently fixed in fx code.
-
Le 24/06/2018 à 21:04, Richard Hipp a écrit :
On 6/24/18, Stéphane Aulery wrote:
Hello,
Le 23/06/2018 à 22:07, Richard Hipp a écrit :
Just FYI:
I have opened up email notifications on the canonical Fossil
repository. To subscribe, visit:
https://fossil-scm.org/fossil/subscribe
Your
On 6/16/18, Stephan Beal wrote:
>
> 3) Fossil effectively uses exit() to handle just about any type of
> non-allocation error. i.e. there's little library-friendly error handling
> in fossil.
Not just errors. If Fossil finds an opportunity to send a "304 Not
Modified" reply, it does so and then
On 6/24/2018 2:04 PM, Richard Hipp wrote:
I do not (yet) have the bounce-processing logic working in the new
email notification system working, and so Fossil was not able to
detect that your confirmation request had bounced.
Thought I'd mention this. My ISP implements an anti-spam technique
On 6/24/18, Stéphane Aulery wrote:
> Hello,
>
> Le 23/06/2018 à 22:07, Richard Hipp a écrit :
>> Just FYI:
>>
>> I have opened up email notifications on the canonical Fossil
>> repository. To subscribe, visit:
>>
>> https://fossil-scm.org/fossil/subscribe
>>
>> Your help in finding creative
Hello,
Le 23/06/2018 à 22:07, Richard Hipp a écrit :
Just FYI:
I have opened up email notifications on the canonical Fossil
repository. To subscribe, visit:
https://fossil-scm.org/fossil/subscribe
Your help in finding creative ways of breaking the new system is appreciated.
I subscrib
On 6/24/18, Dingyuan Wang wrote:
>
> I just got 50 exactly same "[fossil-src] activity alert" emails
Thanks for the report. The problem should be fixed now.
There is a variable in the database that remembers when the last
digest was sent. Do to a missed COMMIT, that variable was never being
up
On Sat 23 Jun 2018 4:07 PM, Richard Hipp wrote:
> Just FYI:
>
> I have opened up email notifications on the canonical Fossil
> repository. To subscribe, visit:
>
> https://fossil-scm.org/fossil/subscribe
>
> Your help in finding creative ways of breaking the new system is appreciated.
Not
Hello,
I previously set to receive these before unsubscribing:
[x] Announcements
[x] Check-ins
[ ] Ticket changes
[x] Wiki
[x] Daily digest only
I just got 50 exactly same "[fossil-src] activity alert" emails
describing 5 check-ins in three minutes. What's happening to the server?
Besides the m
On Sun, 24 Jun 2018 12:22:07 +0200, Richard Hipp wrote:
On 6/24/18, j. van den hoff wrote:
On Sun, 24 Jun 2018 12:08:30 +0200, Richard Hipp wrote:
The UPDATE syntax error should be fixed now. Please try it again.
yes, it works now. thank you. NB: I received the notification email
rega
On 6/24/18, j. van den hoff wrote:
> On Sun, 24 Jun 2018 12:08:30 +0200, Richard Hipp wrote:
>
>> The UPDATE syntax error should be fixed now. Please try it again.
>
> yes, it works now. thank you. NB: I received the notification email
> regarding the fix prior to actually confirming the subscri
On Sun, 24 Jun 2018 12:08:30 +0200, Richard Hipp wrote:
The UPDATE syntax error should be fixed now. Please try it again.
yes, it works now. thank you. NB: I received the notification email
regarding the fix prior to actually confirming the subscription again --
so my confirmation went t
The UPDATE syntax error should be fixed now. Please try it again.
On 6/24/18, j. van den hoff wrote:
> I get an sqlite error when following the verification link and hitting the
>
> `submit' button there:
>
> SQLITE_ERROR: near "WHERE": syntax error
>
> Database Error
> near "WHERE": syntax erro
I get an sqlite error when following the verification link and hitting the
`submit' button there:
SQLITE_ERROR: near "WHERE": syntax error
Database Error
near "WHERE": syntax error: {UPDATE subscriber SET sdonotcall=0,
sdigest=0, ssub='c', smtime=julianday('now'), smip='*', WHERE
subsc
18 matches
Mail list logo
