From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Version file from Feb LTP release still contains 20100131
Date: Wed, 3 Mar 2010 16:20:28 +0530 [thread overview]
Message-ID: <20100303105028.GC23601@linux.vnet.ibm.com> (raw)
In-Reply-To: <4B8E3C08.2080901@in.ibm.com>
On Wed, Mar 03, 2010 at 04:08:00PM +0530, Sachin Sant wrote:
> Not a major issue, but noticed something with latest LTP tarball
> from Feb.
Actually the script design is like that, it will update the version file
once you compiled and build, reading from Changelog.
Can you confirm if you are not having Changelog starting from :
LTP-20100228 .
Mostly it will not be there as you would have extracted next branch. But
it will be always available with master branch.
Thanks
Rishi
>
> The Version file still contains 20100131.
>
> :/home/sachin/work # cat ltp-full-20100228/Version LTP-20100131
> :/home/sachin/work #
>
> Should this be 20100228 ?
>
--
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-03-03 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 10:38 [LTP] Version file from Feb LTP release still contains 20100131 Sachin Sant
2010-03-03 10:50 ` Rishikesh K Rajak [this message]
2010-03-03 11:58 ` Garrett Cooper
2010-03-03 13:57 ` Garrett Cooper
2010-03-03 15:20 ` Sachin Sant
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=20100303105028.GC23601@linux.vnet.ibm.com \
--to=risrajak@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=sachinp@in.ibm.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