From: Dave Jones <davej@codemonkey.org.uk>
To: Ben Collins <bcollins@debian.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>
Subject: Re: Notification hooks
Date: Mon, 16 Dec 2002 17:19:25 +0000 [thread overview]
Message-ID: <20021216171925.GC15256@suse.de> (raw)
In-Reply-To: <20021216171218.GV504@hopper.phunnypharm.org>
On Mon, Dec 16, 2002 at 12:12:18PM -0500, Ben Collins wrote:
> Linus, is there anyway I can request a hook so that anything that
> changes drivers/ieee1394/ in your repo sends me an email with the diff
> for just the files in that directory, and the changeset log? Is this
> something that bkbits can do?
>
> I'd bet lots of ppl would like similar hooks for their portions of the
> source.
It'd be nice if the bkbits webpage had a "notify me" interface for files
in Linus' repository. This way not just the maintainers, but folks
interested in changes in that area can also see the changes.
As well as opening this up for more people, it'd also take the load
of Linus having to do it.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-12-16 17:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 17:12 Notification hooks Ben Collins
2002-12-16 17:18 ` Arjan van de Ven
2002-12-16 17:21 ` Larry McVoy
2002-12-16 17:27 ` Ben Collins
2002-12-16 17:28 ` Arjan van de Ven
2002-12-16 17:44 ` Ben Collins
2002-12-17 9:05 ` David Woodhouse
2002-12-17 13:18 ` Ben Collins
2002-12-16 17:19 ` Dave Jones [this message]
2002-12-16 17:23 ` Ben Collins
2002-12-16 17:25 ` Larry McVoy
2002-12-16 17:24 ` Larry McVoy
2002-12-16 18:25 ` Dave Jones
2002-12-19 6:34 ` Joseph Fannin
2002-12-19 18:02 ` Randy.Dunlap
2002-12-16 17:22 ` Greg KH
2002-12-16 17:34 ` Christoph Hellwig
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=20021216171925.GC15256@suse.de \
--to=davej@codemonkey.org.uk \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.