From: chrubis@suse.cz
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Spelling "succeded" VS. "succeeded"
Date: Wed, 16 Jan 2013 15:05:29 +0100 [thread overview]
Message-ID: <20130116140529.GA6699@rei> (raw)
In-Reply-To: <CA+icZUUsDzP+uLWD0i=JpMSiK1Qu3Pdux19rE7wTeJJu+-FaZw@mail.gmail.com>
Hi!
> While looking trough the results especially searching for some
> pattern, I noticed the different spelling of the word "succeeded" VS.
> "succeded".
> The spell-checker integrated in Firefox v18.0 tells me "succeeded"
> with double-e is correct.
>
> [ SUCCEDED - one "E" ]
>
> $ egrep -i 'error|fail'
> runltplite-results_3.8.0-rc3-next20130116-2-iniza-generic.txt | egrep
> -i succeded
> flock01 1 TPASS : flock() succeded with Shared Lock, returned
> error number=0
> flock01 2 TPASS : flock() succeded with Unlock, returned error number=0
> flock01 3 TPASS : flock() succeded with Exclusive Lock,
> returned error number=0
>
> [ SUCCEEDED - double "E" ]
>
> $ egrep -i 'error|fail'
> runltplite-results_3.8.0-rc3-next20130116-2-iniza-generic.txt | egrep
> -i succeeded
> madvise02 5 TFAIL : madvise succeeded unexpectedly
> open call succeededopen failed with EACCES as expectedopen call
> succeeded<<<execution_status>>>
>
> AFAICS flock01.c needs to be corrected:
>
> --- ltp-full-20120903.orig/testcases/kernel/syscalls/flock/flock01.c
> 2012-09-03 06:39:27.000000000 +0200
> +++ ltp-full-20120903/testcases/kernel/syscalls/flock/flock01.c
> 2013-01-16 14:12:36.597859952 +0100
> @@ -128,7 +128,7 @@ int main(int argc, char **argv)
> continue; /*next loop for MTKERNEL */
> } else {
> tst_resm(TPASS,
> - "flock() succeded with %s,
> returned error number=%d",
> + "flock() succeeded with %s,
> returned error number=%d",
> test_cases[i].opt, TEST_ERRNO);
> }
>
> Not sure if you like that patch sent via git-email as a separate patch?
There is no need for such elaborate explanation for a patch fixing a typo ;).
The ideal way of sending a patches here is unified diff with
signed-of-by line (you can generate these by git format-patch or use git
send-email to mail them directly).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-01-16 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:15 [LTP] Spelling "succeded" VS. "succeeded" Sedat Dilek
2013-01-16 14:02 ` shubham
2013-01-16 14:28 ` Sedat Dilek
2013-01-16 14:51 ` chrubis
2013-01-16 14:05 ` chrubis [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=20130116140529.GA6699@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=sedat.dilek@gmail.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.