From: Kyle Moffett <mrmacman_g4@mac.com>
To: Greg KH <greg@kroah.com>
Cc: Tejun Heo <htejun@gmail.com>,
ebiederm@xmission.com, cornelia.huck@de.ibm.com,
stern@rowland.harvard.edu, kay.sievers@vrfy.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET 4/4] sysfs: implement new features
Date: Thu, 27 Sep 2007 18:38:59 -0400 [thread overview]
Message-ID: <9632E683-2521-49F3-8EB6-64D406862831@mac.com> (raw)
In-Reply-To: <20070925225005.GB26099@kroah.com>
On Sep 25, 2007, at 18:50:05, Greg KH wrote:
> On Thu, Sep 20, 2007 at 05:31:37PM +0900, Tejun Heo wrote:
>> * Name-formatting for symlinks. e.g. symlink pointing to /dira/
>> dirb/leaf can be named as "symlink:%1-%0" and it will show up as
>> "symlink:dirb-leaf". This only applies when new interface is used.
>
> Is this really necessary? It looks like we are adding a "special"
> type of parser here that no one uses.
IMHO this would be nicer if it could reuse existing sprintf code to
handle all the nice shiny sprintf format specifiers. The only
challenge would be how to dynamically build a varargs list from an
array of component names although perhaps there could be an internal
__csprintf function which took a callback for retrieving arguments.
Also since all of the path components are strings I don't know that
numeric specifiers could be made useful, so perhaps it's not the
greatest idea.
I think the primary importance for this functionality is:
>> * Autorenaming of symlinks according to the name format string
>> when target or one of its ancestors is renamed or moved. This
>> only applies when new interface is used.
>
> Nice.
Cheers,
Kyle Moffett
prev parent reply other threads:[~2007-09-27 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 8:31 Tejun Heo
2007-09-20 8:31 ` [PATCH 2/8] sysfs: add name formatting support for symlinks Tejun Heo
2007-09-20 8:31 ` [PATCH 1/8] sysfs: notify file on deactivation Tejun Heo
2007-09-20 8:31 ` [PATCH 6/8] sysfs: implement plugged creation of sysfs nodes Tejun Heo
2007-09-20 8:31 ` [PATCH 3/8] sysfs: chain symlinks to their targets Tejun Heo
2007-09-20 8:31 ` [PATCH 4/8] sysfs: implement symlink auto-removal Tejun Heo
2007-09-20 8:31 ` [PATCH 7/8] sysfs: implement batch error handling Tejun Heo
2007-09-20 8:31 ` [PATCH 5/8] sysfs: implement symlink auto-rename Tejun Heo
2007-09-20 8:31 ` [PATCH 8/8] sysfs: add copyrights Tejun Heo
2007-09-25 22:50 ` [PATCHSET 4/4] sysfs: implement new features Greg KH
2007-09-27 12:24 ` Tejun Heo
2007-09-27 22:38 ` Kyle Moffett [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=9632E683-2521-49F3-8EB6-64D406862831@mac.com \
--to=mrmacman_g4@mac.com \
--cc=cornelia.huck@de.ibm.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®