From: Arjan van de Ven <arjanv@redhat.com>
To: Ben Collins <bcollins@debian.org>
Cc: Larry McVoy <lm@work.bitmover.com>,
Arjan van de Ven <arjanv@redhat.com>,
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:28:38 +0000 [thread overview]
Message-ID: <20021216172838.B976@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021216172722.GX504@hopper.phunnypharm.org>; from bcollins@debian.org on Mon, Dec 16, 2002 at 12:27:22PM -0500
On Mon, Dec 16, 2002 at 12:27:22PM -0500, Ben Collins wrote:
> > bk help triggers.
>
> Well, if it affects more than just the files I am interested in, I only
> want the diff for those files, but the changeset log and files-affected
> for the whole changeset.
>
> If I want the full diff I can go to bkbits or the archive of the commit
> list.
well grepdiff and filterdiff can do that I bet...
filterdiff takes a wildcard and only lets patches through that touch files
that match this wildcard...
next prev parent reply other threads:[~2002-12-16 17:21 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 [this message]
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
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=20021216172838.B976@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=lm@work.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.