From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] symlink only rules support
Date: Mon, 01 Mar 2004 22:27:13 +0000 [thread overview]
Message-ID: <20040301222713.GD10851@kroah.com> (raw)
In-Reply-To: <20040222095013.GD4873@localhost.localdomain>
On Sat, Feb 28, 2004 at 05:57:24PM +0300, Andrey Borzenkov wrote:
> On Saturday 28 February 2004 04:04, Greg KH wrote:
> > On Sun, Feb 22, 2004 at 12:50:13PM +0300, Andrey Borzenkov wrote:
> > > On Tue, Feb 17, 2004 at 09:29:53AM -0800, Greg KH wrote:
> > > > > What about the second part (allow symlink-only rules)?
> > > >
> > > > Yes, I think that would be good to have too. Just split the patches up
> > > > into two pieces, only one patch per feature/fix.
> > >
> > > Slightly modified version. It is less aggressive in that it just adds
> > > symlink collection but otherwise behaves exactly like current code.
> > >
> > > the patch is relative to previous one (configuration directory support).
> >
> > Hm, as Kay modified that one, and things have changed enough, can you
> > resend this against the 019 release?
> >
>
> attached
Thanks for persisting, I've applied this. Care to write up a
documentation patch so that people know how to use this now?
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-03-01 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 9:50 [PATCH] symlink only rules support Andrey Borzenkov
2004-02-28 1:04 ` Greg KH
2004-02-28 14:57 ` Andrey Borzenkov
2004-03-01 22:27 ` Greg KH [this message]
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=20040301222713.GD10851@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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 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.