From: chrubis@suse.cz
To: Simon Xu <xu.simon@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Update sctp testsuite
Date: Tue, 3 Dec 2013 13:44:03 +0100 [thread overview]
Message-ID: <20131203124403.GA28667@rei> (raw)
In-Reply-To: <529D37F5.3000907@oracle.com>
Hi!
> >> Could anyone help to review?
> > Can we move it to the utils/ directory?
>
> OK with me.
>
> > It's an externally developed testsuite so it shouldn't be placed
> > randomly in the LTP tree.
> >
> > And what version of the testsuite is this, latest release or latest git?
>
> The latest git.
Wouldn't latest release suffice?
We will have to synchronize the sources in the future too and bumping it
to latest release when available is one of the reasonable strategies.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&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-12-03 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 7:12 [LTP] [PATCH] Update sctp testsuite Simon Xu
2013-11-25 13:40 ` Simon Xu
2013-12-02 14:20 ` chrubis
[not found] ` <529D37F5.3000907@oracle.com>
2013-12-03 12:44 ` chrubis [this message]
2013-12-06 3:51 ` [LTP] [PATCH] Move sctp to utils and bump it to 1.0.15 Simon Xu
2013-12-09 13:35 ` chrubis
[not found] ` <52A5D4CE.6020207@oracle.com>
2013-12-09 15:44 ` chrubis
[not found] ` <52A67222.6080203@oracle.com>
2013-12-10 11:21 ` 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=20131203124403.GA28667@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=xu.simon@oracle.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