mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Robert Love <rml@novell.com>
Cc: mpm@selenic.com, ttb@tentacle.dhs.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org, gamin-list@gnome.org
Subject: Re: [patch] make dnotify compile-time configurable
Date: Fri, 1 Oct 2004 10:30:21 -0700	[thread overview]
Message-ID: <20041001103021.575d6d48.rddunlap@osdl.org> (raw)
In-Reply-To: <1096651808.7676.28.camel@betsy.boston.ximian.com>

On Fri, 01 Oct 2004 13:30:08 -0400 Robert Love wrote:

| On Fri, 2004-10-01 at 12:27 -0500, Matt Mackall wrote:
| 
| > > In this case I offer A or A&B.
| > 
| > The configurable dnotify patch makes sense on its own and is perhaps
| > less contentious. Push it first and resolve the conflicts with inotify
| > later..
| 
| ..the A above is dnotify by itself.  All I said--and I don't know why
| anyone questioned it--is that I want to put dnotify's configurability in
| the inotify patch.  They make sense together, and the patches conflict
| anyways.  I can do this.

You can do that.  Go ahead.
Even if it isn't clear that they make sense together.
Lots of patches conflict, but that's no grand reason to combine them.

| CONFIG_DNOTIFY makes sense either way, on its own or (more so) with
| inotify, and I already posted the patch separately.
| 
| Why are we even talking about this?!?

I'm going quiet on it...


-- 
~Randy

  reply	other threads:[~2004-10-01 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01  6:24 Robert Love
2004-10-01 15:11 ` Matt Mackall
2004-10-01 15:21   ` Robert Love
2004-10-01 15:31     ` Randy.Dunlap
2004-10-01 15:44       ` Robert Love
2004-10-01 15:58         ` Randy.Dunlap
2004-10-01 17:01           ` Robert Love
2004-10-01 17:27             ` Matt Mackall
2004-10-01 17:30               ` Robert Love
2004-10-01 17:30                 ` Randy.Dunlap [this message]
2004-10-01 17:37                   ` Robert Love
2004-10-01 17:38                     ` Randy.Dunlap

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=20041001103021.575d6d48.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=gamin-list@gnome.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=rml@novell.com \
    --cc=ttb@tentacle.dhs.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

Powered by JetHome