Hi! > 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.
Adding tags to git for stable releases is IMHO good idea. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ 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
