From: Rich Johnston <rjohnston@sgi.com>
To: Dwight Engen <dwight.engen@oracle.com>,
Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: generic/317 use relative paths to avoid traversal permission problems
Date: Mon, 4 Nov 2013 14:43:13 -0600 [thread overview]
Message-ID: <527806E1.3090704@sgi.com> (raw)
In-Reply-To: <20131030143050.34a3b120@oracle.com>
This has been committed.
Thanks
--Rich
commit 4818302fbf5c4c64dbe2fb3e504e71ceafff50e3
Author: Dwight Engen <dwight.engen@oracle.com>
Date: Wed Oct 30 18:30:50 2013 +0000
xfstests: generic/317 use relative paths to avoid traversal
permission problems
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-11-04 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131024161235.GA29381@infradead.org>
[not found] ` <20131024162557.6dd72435@oracle.com>
2013-10-25 9:33 ` xfstests 317 Christoph Hellwig
2013-10-28 15:43 ` Dwight Engen
2013-10-30 16:19 ` Christoph Hellwig
2013-10-30 16:24 ` Christoph Hellwig
2013-10-30 18:30 ` [PATCH] xfstests: generic/317 use relative paths to avoid traversal permission problems Dwight Engen
2013-10-31 15:40 ` Christoph Hellwig
2013-11-04 20:43 ` Rich Johnston [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=527806E1.3090704@sgi.com \
--to=rjohnston@sgi.com \
--cc=dwight.engen@oracle.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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