From: Larry McVoy <lm@bitmover.com>
To: Eli Carter <eli.carter@inet.com>
Cc: Larry McVoy <lm@bitmover.com>,
dri-devel@lists.sourceforge.net, Jeff Garzik <jgarzik@pobox.com>,
davej@redhat.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Dri-devel] Re: [PATCH] CodingStyle fixes for drm_agpsupport
Date: Thu, 14 Aug 2003 13:22:07 -0700 [thread overview]
Message-ID: <20030814202207.GC16291@work.bitmover.com> (raw)
In-Reply-To: <3F3BEF30.5000201@inet.com>
On Thu, Aug 14, 2003 at 03:21:04PM -0500, Eli Carter wrote:
> >Besides, your point is content specific. People check things other than
> >C code into BK.
>
> I assume you can have content-specific validators run before a commit?
bk help triggers
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-08-14 20:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 15:59 [PATCH] CodingStyle fixes for drm_agpsupport davej
2003-08-11 16:40 ` Larry McVoy
2003-08-11 16:58 ` Jeff Garzik
2003-08-11 17:04 ` Larry McVoy
2003-08-11 17:15 ` Jeff Garzik
2003-08-11 17:23 ` Larry McVoy
2003-08-11 17:53 ` Jeff Garzik
2003-08-11 17:59 ` Larry McVoy
2003-08-11 18:11 ` Jeff Garzik
2003-08-11 19:09 ` [Dri-devel] " Philip Brown
2003-08-12 12:07 ` Peter "Firefly" Lund
2003-08-12 10:00 ` Werner Almesberger
2003-08-13 19:44 ` Jamie Lokier
2003-08-14 14:21 ` Eli Carter
2003-08-14 14:47 ` Larry McVoy
2003-08-14 15:18 ` Eli Carter
2003-08-14 15:28 ` Larry McVoy
2003-08-14 19:01 ` Gene Heskett
2003-08-14 18:43 ` [Dri-devel] " Philip Brown
2003-08-14 18:59 ` Randy.Dunlap
2003-08-14 20:16 ` Larry McVoy
2003-08-14 20:21 ` Eli Carter
2003-08-14 20:22 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-11 20:21 Sottek, Matthew J
2003-08-12 7:11 ` Ryan Anderson
2003-08-12 12:05 ` Peter "Firefly" Lund
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=20030814202207.GC16291@work.bitmover.com \
--to=lm@bitmover.com \
--cc=davej@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=eli.carter@inet.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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