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: Mon, 5 Aug 2013 14:11:36 +0200 [thread overview]
Message-ID: <20130805121135.GB8739@rei> (raw)
In-Reply-To: <20130802013524.GN14331@localhost.localdomain>
Hi!
> > > Still at the old SF place: http://lksctp.org/
> > > Git repo from the website: git://github.com/borkmann/lksctp-tools.git
> >
> > So what about making it git submodule or including it only in the
> > released tarballs leaving only a README with URL to the original project
> > in the git?
> >
> > It IMHO does not make much sense to have the code in two different git
> > repos and synchronizing them from time to time with really big patch is
> > even worse.
>
> The lksctp-tools project provides a Linux user space library for SCTP
> (libsctp) including C language header files (netinet/sctp.h) for accessing
> SCTP specific application programming interfaces not provided by the standard
> sockets, and also some helper utilities around SCTP.
>
> The sctp test case is only a little part of lksctp-tools and used for
> sctp protocol stack testing. LTP include these test cases from 2002 for
> networking test. It is just like TCP/UDP/ICMP/IGMP testing. I don't see any
> reason why we should remove it from network stack testing.
I haven't said we should remove them from LTP. I'm just trying to figure
out if we can do better than having the sources maintained in two git
repos at the same time which is more work and prone to mistakes.
--
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
prev parent reply other threads:[~2013-08-05 12:11 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
[not found] ` <51F92131.7090406@redhat.com>
2013-08-01 13:33 ` chrubis
[not found] ` <20130802013524.GN14331@localhost.localdomain>
2013-08-05 12:11 ` 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=20130805121135.GB8739@rei \
--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).