From: Larry McVoy <lm@bitmover.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Larry McVoy <lm@bitmover.com>, cliff white <cliffw@osdl.org>,
hannal@us.ibm.com, lse-tech@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Amy Graf <amy@work.bitmover.com>
Subject: Re: [Lse-tech] Re: Minutes from OSDL talk at LSE call today
Date: Tue, 9 Dec 2003 13:48:15 -0800 [thread overview]
Message-ID: <20031209214815.GA32633@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312091625560.2313@montezuma.fsmlabs.com>
On Tue, Dec 09, 2003 at 04:26:45PM -0500, Zwane Mwaikambo wrote:
> On Thu, 4 Dec 2003, Larry McVoy wrote:
>
> > > The first is triggers. The Mozilla tinderbox is driven by triggers from
> > > CVS commits. I believe that triggers are resevered for the commercial
> > > version of BK.
> >
> > That's not true. Trigger support is identical in both versions.
>
> Perhaps the FAQ may need updating then;
>
> http://www.bitkeeper.com/Documentation.FAQS.Event.html
Indeed.
It's worth pointing out that triggers in open source trees are quite a bit
more dangerous than in controlled environment. Carl-Daniel's boss made
quite a fuss over the fact that triggers are just programs that are run
and can be used to cause all sorts of problems if people were malicious.
I've toyed with the idea of disabling triggers in openlogging trees
because of this. I'm neutral on the topic, it's not like triggers
are some huge money maker that we need to reserve for the commercial
version. If the general feeling is that triggers are useful and people
will take responsibility for policing their own repos then we'll leave
them in. On the other hand, if someone putting a nasty trigger into
your tree somehow becomes the fault of BitMover because we provided the
infrastructure then out they go in the next release.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-12-09 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 1:20 Minutes from OSDL talk at LSE call today Hanna Linder
2003-12-04 3:35 ` Larry McVoy
2003-12-04 21:45 ` [Lse-tech] " cliff white
2003-12-04 22:54 ` Chris Wright
2003-12-04 23:44 ` Larry McVoy
2003-12-09 18:53 ` cliff white
2003-12-09 21:26 ` Zwane Mwaikambo
2003-12-09 21:48 ` Larry McVoy [this message]
2003-12-09 21:54 ` Zwane Mwaikambo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031209214815.GA32633@work.bitmover.com \
--to=lm@bitmover.com \
--cc=amy@work.bitmover.com \
--cc=cliffw@osdl.org \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=zwane@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).