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: > On Fri, Feb 4, 2011 at 10:44 AM, Brian Long > <[email protected]> wrote: > > I would like to know if there's a straightforward way to > track the changes > > between successive releases of mythtv 0.24-fixes. > > > 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. The previous commit version was "v0.24-135-g8921ded", e.g. 15 commits before the current one and was commit "8921ded85a092988be40". > The old "Trac" page let me input two SVN revision numbers and generate > a list of commit messages. Many of those commit messages had > auto-links to the bugs. I don't see this with github, but I've just > started poking around. I guess the transition will require some time to settle in. I'm not that comfortable either, I do miss the linearity of svn, but OTOH a big advantage of git is its non-linearity. Anyway, what matters is how developers can better work on the code and not how we extract it. :) > I don't want to download the entire src tree from git just to look up > revision changes, etc. I was hoping I was missing something simple. I hope some of my comments make it a bit clearer. -- http://thimm.gr/ - http://ATrpms.net/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
