On 2018-06-22 20:40, Joerg Sonnenberger wrote:
[---]
> BTW, the main mercurial list uses the following mail format for "batch"
> changes:
>
> https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-June/117551.html
This is highly machine parse-friendly. I like it a lot.
--
Kind Regards
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.
-
On Fri, Jun 22, 2018 at 02:18:35PM -0400, Richard Hipp wrote:
> Shown below is what I have at the moment. It is more succinct than
> other examples I've seen, but you can easily follow the link for
> details.
BTW, the main mercurial list uses the following mail format for "batch"
changes:
https:
On Jun 22, 2018, at 12:18 PM, Richard Hipp wrote:
>
> == 2018-06-22 01:28:10 Check-In ==
> Fix harmless compiler warnings. (user: drh tags: email-alerts)
> https://fossil-scm.org/fossil/info/5fde17bbbc2cba69d3f8
Some systems I’ve used in the past have an option to include a diff on
checkins. T
On 22 June 2018 at 11:18, Richard Hipp wrote:
> Shown below is what I have at the moment. It is more succinct than
> other examples I've seen, but you can easily follow the link for
> details.
Very nice! I think you're on the right track!
___
fossil-u
Shown below is what I have at the moment. It is more succinct than
other examples I've seen, but you can easily follow the link for
details.
The example below has more check-ins that one would normally find in a
single alert (unless you sign up for the "daily digest") because my
local repo is not
On 22 June 2018 at 07:09, jungle Boogie wrote:
> On 22 June 2018 at 06:09, Richard Hipp wrote:
>> You may have noticed that I've been working on adding support for
>> email notifications or alerts to events on a Fossil repository. But I
>> need your help.
>>
>> When an event occurs (such as a ch
On Fri, Jun 22, 2018 at 09:09:11AM -0400, Richard Hipp wrote:
> When an event occurs (such as a check-in, or wiki-page edit) and a
> user wants a notification of that event, what should the email look
> like?
What I am using for the Mercurial tests is the following:
https://mail-index.netbsd.org/
Personally I would like something simple such as:
Subject line: New check-in on fossil
drh made a check-in on branch trunk.
Comment: Add a new capability that allows signup for email
notification. Change the name of the older "EMail" privilege to
"View-PII" to avoid confusion.
Date: 2018-0
On Fri, 22 Jun 2018 16:46:07 +0200, Marcelo wrote:
El vie., 22 jun. 2018 a las 11:09, jungle Boogie
()
escribió:
I'd rather have emails delivered in plain text, bypassing
html/markdown but that's just my preference.
+1 for plain text notifications.
+1
--
Using Opera's revolutionar
Yes, plain text please since hyperlinks will point to richer content.
On Fri, Jun 22, 2018 at 10:46 AM, Marcelo wrote:
> El vie., 22 jun. 2018 a las 11:09, jungle Boogie ()
> escribió:
>
>>
>> I'd rather have emails delivered in plain text, bypassing
>> html/markdown but that's just my preferenc
El vie., 22 jun. 2018 a las 11:09, jungle Boogie ()
escribió:
>
> I'd rather have emails delivered in plain text, bypassing
> html/markdown but that's just my preference.
>
+1 for plain text notifications.
--
o-=< Marcelo >=-o
___
fossil-users
On 22 June 2018 at 06:09, Richard Hipp wrote:
> You may have noticed that I've been working on adding support for
> email notifications or alerts to events on a Fossil repository. But I
> need your help.
>
> When an event occurs (such as a check-in, or wiki-page edit) and a
> user wants a notific
On 6/22/18, Philip Bennefall wrote:
> Would it make sense to have the possibility to supply various email
> templates in markdown on an admin page, and have insertable variables?
> Of course with a default text for each new repo.
That sounds like good idea. Please send an example. Ideally, your
Would it make sense to have the possibility to supply various email
templates in markdown on an admin page, and have insertable variables?
Of course with a default text for each new repo.
Kind regards,
Philip Bennefall
P.S. Email notifications are a very welcome addition for us. Thank you!
You may have noticed that I've been working on adding support for
email notifications or alerts to events on a Fossil repository. But I
need your help.
When an event occurs (such as a check-in, or wiki-page edit) and a
user wants a notification of that event, what should the email look
like?
Ple
16 matches
Mail list logo
