public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Marioh mrs <marios.makris@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP and GSOC
Date: Fri, 27 Apr 2012 07:39:55 +0800	[thread overview]
Message-ID: <4F99DCCB.5040707@cn.fujitsu.com> (raw)
In-Reply-To: <CAMYrgfR6StoOvo8CNSFFXB6foctU2itACuQwAtxBsAJ1wDK0Ow@mail.gmail.com>

On 04/27/2012 03:10 AM, Marioh mrs wrote:

>> So let me introduce you to Marios Makris who will be working on LTP
>> during this summer. The plan is to code cleanup and documentation for
>> LTP test interface as well as implementing/cleanup syscall tests. Be
>> nice to him ;).
>>
>> Also CCing him directly so he could introduce himself.
>>
>> --
>> Cyril Hrubis
> 
> Hey everyone,
> 
> To begin with, great work everyone :)
> 
> I am Marios, a level 6 BSc CS student at uni of Hertfordshire and will
> be working on ltp through GSoC for the summer (hopefully after the
> GSoC aswell :)).
> The plan is to cleanup and document the test interface as well as
> cleanup and implementation of syscalls tests. The outcome of the
> project will hopefully make the maintenance a little easier :)
> 
> I hope for the best cooperation, please feel free if you want to ask
> me anything.
> 
> PS1. Thanks Cyril for the introduction :)
> PS2. Sorry for my late responce just got back from uni.



Welcome!

Thanks,
Wanlong Gao

> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2012-04-26 23:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 14:31 [LTP] LTP and GSOC Cyril Hrubis
     [not found] ` <CAMYrgfR6StoOvo8CNSFFXB6foctU2itACuQwAtxBsAJ1wDK0Ow@mail.gmail.com>
2012-04-26 19:17   ` Marioh mrs
2012-04-26 23:39   ` Wanlong Gao [this message]
2012-04-27  7:47   ` Shubham Goyal
2012-04-27  3:54 ` Caspar Zhang
  -- strict thread matches above, loose matches on Subject: below --
2019-02-26 12:03 [LTP] LTP and GSoC Cyril Hrubis

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=4F99DCCB.5040707@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=marios.makris@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox