From: "Tim Pepper" <lnxninja@us.ibm.com>
To: viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org, "Linda Walsh" <lkml@tlinx.org>,
"Brian D. McGrew" <brian@visionpro.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Too many levels of symbolic links
Date: Thu, 18 May 2006 12:20:03 -0700 [thread overview]
Message-ID: <eada2a070605181220l2f038cddlfd7a243ac36cd4af@mail.gmail.com> (raw)
In-Reply-To: <eada2a070605171358r1fea2c62u641b6308e78aa1e4@mail.gmail.com>
Nevermind..missed the subject changed follow up to this...
Tim
prev parent reply other threads:[~2006-05-18 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 18:05 Brian D. McGrew
2006-05-03 1:52 ` Linda Walsh
2006-05-03 2:57 ` H. Peter Anvin
2006-05-03 3:08 ` [PATCH] symlink nesting level change Al Viro
2006-05-04 1:35 ` Andrew Morton
2006-05-04 6:55 ` Arjan van de Ven
2006-05-04 7:19 ` Al Viro
2006-07-13 18:35 ` Tim Pepper
2006-07-13 21:27 ` Andrew Morton
2006-05-17 20:58 ` Too many levels of symbolic links Tim Pepper
2006-05-18 19:20 ` Tim Pepper [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=eada2a070605181220l2f038cddlfd7a243ac36cd4af@mail.gmail.com \
--to=lnxninja@us.ibm.com \
--cc=brian@visionpro.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=viro@zeniv.linux.org.uk \
/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