Thus said Mark Janssen on Thu, 13 Feb 2014 22:06:49 +0100:
> * Email verification to prevent spam.
MLMs (mailing list managers; like ezmlm, mailman, etc...) already solve
this problem. Perhaps those who want notifications can subscribe to a
tic...@domain.dom mailing list and the ticket hook
On Thu, Feb 13, 2014 at 4:06 PM, Mark Janssen wrote:
> Some things that come to mind:
>
> * Ticket notification for admin, logger and followers (this is the big
> one).
> * Email verification to prevent spam.
>
I can think of ways of using a list server to mostly handle these 2 items.
> * Abil
Hi Dr. Hipp,
Thank you for your quick reply, I really appreciate it. Both the options
you provided work perfectly. It took me a little bit of digging to
determine the syntax for specifying an attached file, but eventually
figured it out from a previous mailing list post here,
https://www.mail-arc
On Thu, Feb 13, 2014 at 7:40 PM, Stephen Cripps <9...@queensu.ca> wrote:
> Hello fossil users:
>
> I've been using fossil for some time now, and I'm really blown away by
> the versatility of the program.
>
> I have run into a problem recently however. I would like to be able to
> allow non-members
Hello fossil users:
I've been using fossil for some time now, and I'm really blown away by
the versatility of the program.
I have run into a problem recently however. I would like to be able to
allow non-members to view the wiki for a project, but not the source
code. At the same time, I wish to
I set up our email notification to use a wiki page as the source for email
addresses (creatively named "emailnotification"). Anyone who has read/write
to the wiki can add or remove email addresses. This works fine for us so
far but might not work for a open web facing project.
On Thu, Feb 13, 201
On Thu, Feb 13, 2014 at 9:33 PM, Ron Wilson wrote:
> On Thu, Feb 13, 2014 at 2:46 PM, Mark Janssen wrote:
>
>> True with effort all of this could be retrieved from the underlying
>> sqlite db. The reason I didn't do that is that you need opt out and email
>> verification to prevent sending spam.
On Thu, Feb 13, 2014 at 2:46 PM, Mark Janssen wrote:
> True with effort all of this could be retrieved from the underlying sqlite
> db. The reason I didn't do that is that you need opt out and email
> verification to prevent sending spam. I could add your email on every
> ticket and you would not
On Thu, Feb 13, 2014 at 11:26 AM, Stephan Beal wrote:
> On Thu, Feb 13, 2014 at 8:24 PM, Richard Hipp wrote:
>>
>> Huh. Apparently you can already do "config pull css". What else other
>> than the CSS file needs to be brought over to move a "look" from one repo to
>> another?
>
>
> Didn't know
On 13 Feb 2014 19:44, "Ron Wilson" wrote:
>
> On Thu, Feb 13, 2014 at 1:13 PM, Mark Janssen
wrote:
>>
>> I have used the ticket hooks and they do work. However they will not
allow automatic updates to be sent to whoever logged the ticket.
>> As a result I have moved the bug tracker to redmine.
>
On Thu, Feb 13, 2014 at 8:24 PM, Richard Hipp wrote:
> Huh. Apparently you can already do "config pull css". What else other
> than the CSS file needs to be brought over to move a "look" from one repo
> to another?
>
Didn't know that. In my case i pulled (css,header,footer), but i don't know
i
On Thu, Feb 13, 2014 at 2:18 PM, Stephan Beal wrote:
> On Thu, Feb 13, 2014 at 7:52 PM, Richard Hipp wrote:
>
>> Do we need to change "config pull skin" so that it omits the index page
>> name?
>>
>
> i'd vote for that, or a flag for it.
>
>
Huh. Apparently you can already do "config pull css"
On Thu, Feb 13, 2014 at 7:52 PM, Richard Hipp wrote:
> Do we need to change "config pull skin" so that it omits the index page
> name?
>
i'd vote for that, or a flag for it.
> Or, maybe rig "config pull skin" so that it will accept a URL for a
> repository with a different project code, but on
On Thu, Feb 13, 2014 at 12:09 PM, Stephan Beal wrote:
> On Thu, Feb 13, 2014 at 6:07 PM, Matt Welland wrote:
>
>> Hmmm I thought I could just do a "fossil config pull skin" to get
>> these but that seems not to be sufficient. What are the steps to clone a
>> skin?
>>
>
> conf pull skin pulls
On Thu, Feb 13, 2014 at 1:13 PM, Mark Janssen wrote:
> I have used the ticket hooks and they do work. However they will not allow
> automatic updates to be sent to whoever logged the ticket.
> As a result I have moved the bug tracker to redmine.
>
My impression, from reading comments on this emai
I have used the ticket hooks and they do work. However they will not allow
automatic updates to be sent to whoever logged the ticket.
As a result I have moved the bug tracker to redmine.
On 13 Feb 2014 16:25, "Baptiste Daroussin"
wrote:
> Hi,
>
> I'm using fossil for a while now, and I'm quite ha
On Thu, Feb 13, 2014 at 6:07 PM, Matt Welland wrote:
> Hmmm I thought I could just do a "fossil config pull skin" to get
> these but that seems not to be sufficient. What are the steps to clone a
> skin?
>
conf pull skin pulls not only the CSS but also the index page name, so i've
reverted t
Hmmm I thought I could just do a "fossil config pull skin" to get these
but that seems not to be sufficient. What are the steps to clone a skin?
On Wed, Feb 12, 2014 at 12:40 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:
> I have also stolen long ago the "google code" like th
Hello.
On Thu, Feb 13, 2014 at 04:24:39PM +0100, Baptiste Daroussin wrote:
In particular to interact with the submitter. I have found no way to:
1/ send a mail when new ticket is created (yes we can follow via rss feed,
but a mail is way nicer)
2/ send a mail each time to ticket is modified to r
On Thu, Feb 13, 2014 at 8:24 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:
> Hi,
>
> I'm using fossil for a while now, and I'm quite happy with it, for the scm
> part and the web part.
>
> The problem is when going with the ticket part of fossil.
>
> I do not need something sophist
On Thu, Feb 13, 2014 at 10:24 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:
> In particular to interact with the submitter. I have found no way to:
> 1/ send a mail when new ticket is created (yes we can follow via rss feed,
> but a mail is way nicer)
> 2/ send a mail each time to
Hi,
I'm using fossil for a while now, and I'm quite happy with it, for the scm
part and the web part.
The problem is when going with the ticket part of fossil.
I do not need something sophisticated, the the way the ticket works is ok
with me, however the more the project I'm working on is growin
22 matches
Mail list logo
