From: chrubis@suse.cz
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>,
Daniel Borkmann <dborkman@redhat.com>,
Xie Lingyun <lingyun.xie@bj.cs2c.com.cn>
Subject: Re: [LTP] [PATCH] testcases/network/sctp: update sctp test to upstream version 1.0.15
Date: Wed, 31 Jul 2013 16:34:49 +0200 [thread overview]
Message-ID: <20130731143448.GB2698@rei.scz.novell.com> (raw)
In-Reply-To: <1374548876-24829-1-git-send-email-liuhangbin@gmail.com>
Hi!
> SCTP test in ltp is based on lksctp. But the last patch for sctp in ltp is
> 2006. It has changed a lot and fixed many bugs. Update sctp test to upstream
> version 1.0.15 now.
I'm a bit confused here. Is the SCTP testsuite developed elsewhere? In
that case it probably shouldn't be part of the LTP repo, perhaps a git
submodule as mce-test is.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-07-31 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 3:07 [LTP] [PATCH] testcases/network/sctp: update sctp test to upstream version 1.0.15 Hangbin Liu
2013-07-23 3:27 ` Hangbin Liu
2013-07-31 14:34 ` chrubis [this message]
[not found] ` <51F92131.7090406@redhat.com>
2013-08-01 13:33 ` chrubis
[not found] ` <20130802013524.GN14331@localhost.localdomain>
2013-08-05 12:11 ` chrubis
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=20130731143448.GB2698@rei.scz.novell.com \
--to=chrubis@suse.cz \
--cc=dborkman@redhat.com \
--cc=lingyun.xie@bj.cs2c.com.cn \
--cc=liuhangbin@gmail.com \
--cc=ltp-list@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).