From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: hisashi.hashimoto.wh@hitachi.com
Cc: LTP Mailing List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] GPL License in CrackerJack
Date: Tue, 13 Oct 2009 20:13:43 +0530 [thread overview]
Message-ID: <1255445023.8438.67.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <XNM1$9$0$3$$2$7$9$A$9010029U4ac95f25@hitachi.com>
On Mon, 2009-10-05 at 11:51 +0900, hisashi.hashimoto.wh@hitachi.com
wrote:
> Suburata-san,
> Yamato-san,
>
> This is Hashimoto of CrackerJack.
>
> I inserted License Description into all source code of our project.
> (GPL V2)
> If you need our latest source code,
> please do one of followings.
Thank you Hashimoto-san. We will refer to your code whenever needed.
Regards--
Subrata
>
> SVN
> svn co https://crackerjack.svn.sourceforge.net/svnroot/crackerjack crackerjack
>
> Download tar ball.
> crackerjack-3.0.tgz at http://sourceforge.net/projects/crackerjack/files/
>
> Thanks,
>
> Hisashi Hashimoto
>
> Board of Director, the Linux Foundation,
>
> Senior Engineer
>
> Open Source Software Promotion Center
> Enterprise Business Planning
> Hitachi, Ltd., Software Division
> Tel : +81-45-862-8470, Fax : +81-45-862-8471
> hisashi.hashimoto.wh@hitachi.com
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-10-13 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 2:06 [LTP] [PATCH][openfile] file descriptors not cleaned up Henry Yei
2009-10-04 22:18 ` Jiri Palecek
2009-10-05 2:51 ` [LTP] GPL License in CrackerJack hisashi.hashimoto.wh
2009-10-13 14:43 ` Subrata Modak [this message]
2009-10-05 21:33 ` [LTP] [PATCH][openfile] file descriptors not cleaned up Henry Yei
2009-10-13 14:43 ` Subrata Modak
2009-10-13 19:20 ` Garrett Cooper
2009-10-13 19:21 ` Garrett Cooper
2009-10-14 2:25 ` Henry Yei
2009-10-14 2:30 ` Garrett Cooper
[not found] ` <8368651DACC1964480F951191B94A0780153D6A2@svexch01.mvista.com>
2009-10-15 22:03 ` [LTP] autoconf files Garrett Cooper
2009-10-14 20:28 ` [LTP] [PATCH][openfile] file descriptors not cleaned up Subrata Modak
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=1255445023.8438.67.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=hisashi.hashimoto.wh@hitachi.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