From: Jiri Palecek <jpalecek@web.de>
To: michal.simek@petalogix.com
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] lchown test case
Date: Wed, 06 Jan 2010 02:27:25 +0100 [thread overview]
Message-ID: <4B43E6FD.3020906@web.de> (raw)
In-Reply-To: <4B4204D2.70204@petalogix.com>
Michal Simek napsal(a):
> Hi,
Hi,
>
> I have some problems with lchown02 test which is caused with this patch.
> What is prep_create_link?
>
> Thanks,
> Michal
>
> http://git.kernel.org/?p=linux/kernel/git/galak/ltp.git;a=commitdiff;h=ee1a022fc76076d7fc1b6b1797c195244414c038
>
>
>
> diff --git a/runtest/syscalls b/runtest/syscalls
> index fbe8641..34631ed 100644 (file)
> --- a/runtest/syscalls
> +++ b/runtest/syscalls
> @@ -462,10 +462,10 @@ kill12 kill12
>
> lchown01 lchown01
> lchown01_16 lchown01_16
> -lchown02 cp -p $LTPROOT/testcases/bin/create_link $TMP; lchown02
> -lchown02_16 cp -p $LTPROOT/testcases/bin/create_link $TMP; lchown02_16
> +lchown02 prep_create_link; lchown02
> +lchown02_16 prep_create_link; lchown02_16
IMHO it should do the same as the line above. But I think the whole thing could
be deleted without causing any grief:
http://repo.or.cz/w/ltp-debian.git?a=commit;h=a5499edcf368fa88df924f94ffcbe63c22b46e82
Regards
Jiri Palecek
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-01-06 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 15:10 [LTP] lchown test case Michal Simek
2010-01-06 1:27 ` Jiri Palecek [this message]
2010-01-06 1:41 ` Garrett Cooper
2010-01-06 2:31 ` Garrett Cooper
2010-01-06 12:13 ` Michal Simek
2010-01-06 19:24 ` Garrett Cooper
2010-01-07 1:33 ` Jiri Palecek
2010-01-07 5:57 ` Garrett Cooper
2010-01-07 14:02 ` Michal Simek
2010-01-08 15:40 ` Jiří Paleček
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=4B43E6FD.3020906@web.de \
--to=jpalecek@web.de \
--cc=ltp-list@lists.sourceforge.net \
--cc=michal.simek@petalogix.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 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.