From: Jeff Dike <jdike@addtoit.com>
To: Paul Wagland <paul@kungfoocoder.org>
Cc: user-mode-linux-devel@lists.sourceforge.net, Piotr Neuman <sikkh@wp.pl>
Subject: [uml-devel] Re: A few comments on hostfs interface
Date: Wed, 21 Apr 2004 11:15:19 -0400 [thread overview]
Message-ID: <20040421151519.GB7081@ccure.user-mode-linux.org> (raw)
In-Reply-To: <F87C6818-936D-11D8-B5AA-000A95CD704C@kungfoocoder.org>
On Wed, Apr 21, 2004 at 10:29:13AM +0200, Paul Wagland wrote:
> struct externfs_file_ops:
> Almost all of the functions have the naming form verb_noun, except
> for file_create(). I would suggest to reverse this for the sake of
> consistency.
Yup. I'm schizophrenic on verb-noun vs noun-verb, sometimes within
the same interface, as you've noticed.
>
> Most functions have "long names" that is open_file, link_file,
> access_file, etc. The exceptions to this are mkdir(), rmdir(), mknod(),
> readlink(), and statfs(). This cannot be done to "keep standard
> semantics" since open_dir() is not in it's standard form either. I
> would suggest to rename all of the "short form" functions into the
> standardised form.
Yup.
> Jeff, if you agree with the above, let me know, and you will receive a
> patch for it later today.
OK, can you make it on top of sikkh's patch?
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-04-21 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 8:29 [uml-devel] A few comments on hostfs interface Paul Wagland
2004-04-21 15:15 ` Jeff Dike [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=20040421151519.GB7081@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=paul@kungfoocoder.org \
--cc=sikkh@wp.pl \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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