From: Michael Blandford <mlblandf@sedona.ch.intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: autofs mailing list <autofs@linux.kernel.org>, raven@themaw.net
Subject: Re: An offer to host autofs.org
Date: Tue, 04 May 2004 11:26:35 -0700 [thread overview]
Message-ID: <4097E05B.7060000@sedona.intel.com> (raw)
In-Reply-To: <4097DB47.2050603@zytor.com>
H. Peter Anvin wrote:
> I have several objections to this proposal.
>
> First of all, I still want the full autofs rewrite -- autofs 5 -- done
> at some point, and I think this infrastructure would be in the way.
>
Can you elaborate on why you feel like it would be in the way?
Michael
Disclaimer: The content of this message is my personal opinion only and
although I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak on
behalf of Intel on this matter.
next prev parent reply other threads:[~2004-05-04 18:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 12:58 An offer to host autofs.org raven
2004-05-03 17:55 ` Tim Hockin
2004-05-04 0:32 ` Axel Thimm
2004-05-04 1:10 ` Ian Kent
2004-05-04 1:09 ` Tim Hockin
2004-05-04 1:21 ` humm " Alvin Oga
2004-05-04 12:25 ` Axel Thimm
2004-05-04 14:37 ` mount point created if automount map is empty during daemon startup? Tom Georgoulias
2004-05-04 14:53 ` raven
2004-05-04 15:26 ` Tom Georgoulias
2004-05-04 15:37 ` raven
2004-05-04 15:43 ` Tom Georgoulias
2004-05-04 15:52 ` raven
2004-05-04 15:27 ` raven
2004-05-04 15:05 ` Jeff Moyer
2004-05-04 15:22 ` raven
2004-05-04 15:37 ` Tom Georgoulias
2004-05-04 15:57 ` raven
2004-05-04 20:41 ` Tom Georgoulias
2004-05-05 1:08 ` Ian Kent
2004-05-04 18:04 ` An offer to host autofs.org H. Peter Anvin
2004-05-04 18:21 ` fork - " Alvin Oga
2004-05-04 18:26 ` Michael Blandford [this message]
2004-05-04 21:16 ` Mike Waychison
2004-05-04 21:50 ` Axel Thimm
2004-05-04 22:04 ` Mike Waychison
2004-05-05 1:16 ` Ian Kent
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=4097E05B.7060000@sedona.intel.com \
--to=mlblandf@sedona.ch.intel.com \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
--cc=raven@themaw.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 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.