mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
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 09:22:17 -0800	[thread overview]
Message-ID: <20021216172216.GB15425@kroah.com> (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?

Just subscribe to the bk-commits-head mailing list, and then have
procmail set up a filter to alert you to anything that happens to files
in any specific directories.

Or do something else with the data sent on that mailing list, or look at
the changeset files on kernel.org that are constantly being generated.

There are lots of ways to get this information without relying on hooks
in bk.

Hope this helps,

greg k-h

  parent reply	other threads:[~2002-12-16 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 17:12 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
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 [this message]
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=20021216172216.GB15425@kroah.com \
    --to=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome