From: Sandip Bhattacharya <sandipb@foss-community.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] LTP version in ChangeLog not updated?
Date: Wed, 18 May 2011 18:16:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20110518T201407-12@post.gmane.org> (raw)
I just cloned the LTP git repo from SF and ran the suite. Strangely, the report
showed the LTP version to be an old one. Is something amiss?
$ git log -1
commit 61ac0eaf2a3f24378ed0ab20a1613134ab83843a
Author: Cyril Hrubis <chrubis@suse.cz>
Date: Wed May 11 17:08:32 2011 +0200
Add newline to include/cleanup.c to stop GCC from whining.
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
$ head ChangeLog
LTP-20100831
commit dd59d49d75598d163f1b4599067a9f0dcb70e6c4
Author: Garrett Cooper <yanegomi@gmail.com>
Date: Tue Aug 31 23:09:49 2010 -0700
The cacheflush system call does not return EINVAL in the latest Linux
kernel. see the link:
A related patch about the cacheflush function:
http://lkml.org/lkml/2009/4/9/203
Thanks,
Sandip
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-05-18 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 18:16 Sandip Bhattacharya [this message]
2011-05-18 19:19 ` [LTP] LTP version in ChangeLog not updated? Garrett Cooper
2011-05-19 6:42 ` Sandip Bhattacharya
2011-05-19 13:27 ` Cyril Hrubis
2011-05-19 8:30 ` Shubham Goyal
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=loom.20110518T201407-12@post.gmane.org \
--to=sandipb@foss-community.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