On Fri, Feb 4, 2011 at 3:23 PM, Axel Thimm <[email protected]> wrote: > On Fri, 2011-02-04 at 15:27 -0500, Brian Long wrote: >> On Fri, Feb 4, 2011 at 2:38 PM, David Rees <[email protected]> wrote: >> Here's a crude way of doing it, look here: >> https://github.com/MythTV/mythtv/commits/fixes/0.24 >> >> I don't know enough about git to know why the commit versions in >> Axel's log don't match up with the RPM changelog... > > They do match, I'm using git describe output in the changelog which is > what mythtv's output also uses. Check the man page, it is a more human > accessible commit versioning than the crude commit hash. It counts the > commits from the nearest tag (in this case v0.24), and adds this count > as well as the first characters from the commit tag. > > For example "v0.24-150-g08a8a65" is 150 commits further than the tag > "v0.24" and the commits starts with "08a8a65", e.g. in this case you can > look it up in the URL you quoted as 08a8a65535638de185e6, the latest > commit as of this writing.
Whoops - totally missed that the rpm changelog has an extra g in the front - now it all makes sense. :) -Dave _______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
