Hi Garrett, > > Updating the ChangeLog is a manual procedure (shouldn't be, but it is).
It is not a major issue at all. Just that the HTML report for the latest stable show the LTP version to be older than the stable build date. That looks a little odd when I claim at work that we are using the latest LTP stable. :-P BTW, for stable builds, do you have a tag or a commit number documented somewhere for the git commit used as the basis of the release? Right now whenever a test fails where it shouldn't, I am doing a whack-a-mole fix from the log of the file involved. If there is a git tag or commit number for the stable, I can look at all the commits from that time onwards to incorporate as patches into my srpm. 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
