Log in

View Full Version : How to obtain x264 Changelog with rev numbers?


laserfan
25th July 2013, 13:14
Changelog by revision, possibly outdated, can be found here: http://x264.nl/x264/changelog.txt
I used to rely on this link in order to know what-commit-is-in-the-latest-release-number but now it's out-of-date.

I can get komisar's unpatched build by latest release number, but how do I know what changes are therein, i.e. how to relate http://git.videolan.org/gitweb.cgi?p=x264.git;a=shortlog to a release number?

:confused:

LoRd_MuldeR
6th August 2013, 10:44
I used to rely on this link in order to know what-commit-is-in-the-latest-release-number but now it's out-of-date.

I can get komisar's unpatched build by latest release number, but how do I know what changes are therein, i.e. how to relate http://git.videolan.org/gitweb.cgi?p=x264.git;a=shortlog to a release number?

:confused:

Git doesn't use revision numbers, like SVN did.

Each commit is identified by a SHA-1 hash. If you want a revision number, you have to count the number of commits in the "master" branch.

It's actually straight forward using a simple script, but I put together a little tool for exactly that purpose:
git2rev.exe (https://code.google.com/p/mulder/source/browse/trunk/libx264/git2rev.exe) (Click on "View raw file" to download)

Usage:
git log > Changelog.txt
git2rev.exe Changelog.txt

kabelbrand
6th August 2013, 14:30
So the moderators moved laserfan's question but deleted my answer. Thanks...

what-commit-is-in-the-latest-release-number

If you run x264 --version you get something like this: x264 0.135.2345 f0c1c53

Just find the commit hash starting with f0c1c53 in the git log, e.g.
f0c1c53d58420d209f0fb7b63e49125ab1c85aa7 (http://git.videolan.org/gitweb.cgi?p=x264.git;a=shortlog;h=f0c1c53d58420d209f0fb7b63e49125ab1c85aa7)

LoRd_MuldeR
6th August 2013, 15:43
So the moderators moved laserfan's question but deleted my answer. Thanks...

The sticky thread is not for discussion!

Posts in the sticky thread will usually either be deleted or moved - depending on their relevance.

Better avoid posting in the sticky thread altogether. Start a new thread, when appropriate...

kabelbrand
6th August 2013, 16:12
The sticky thread is not for discussion!

Yes, I noticed after my post disappeared. Newbie mistake... It just would have been nice to get an info beforehand or have both question and answer moved. Never mind :)

laserfan
6th August 2013, 17:28
Git doesn't use revision numbers, like SVN did.

Each commit is identified by a SHA-1 hash. If you want a revision number, you have to count the number of commits in the "master" branch.

It's actually straight forward using a simple script, but I put together a little tool for exactly that purpose:
git2rev.exe (https://code.google.com/p/mulder/source/browse/trunk/libx264/git2rev.exe) (Click on "View raw file" to download)

Usage:
git log > Changelog.txt
git2rev.exe Changelog.txt
Thanks but unless I'm misunderstanding something, you have to have git on your PC in order to use git2rev, and I do not.

LoRd_MuldeR
6th August 2013, 18:36
Thanks but unless I'm misunderstanding something, you have to have git on your PC in order to use git2rev, and I do not.

Yes. But installing and using Git is not rocket science ;)

1. Install Git from here (http://code.google.com/p/msysgit/downloads/detail?name=Git-1.8.3-preview20130601.exe&can=2&q=full+installer+official+git).
2. Run: Start -> Git -> Git Bash
3. Type "git clone git://git.videolan.org/x264.git x264-src
4. Type "cd x264-src"
5. Type "git log > Changelog.txt"
6. Type "git2rev.exe Changelog.txt"

Once you have clone'd x264 to your local HDD, you can just do:
1. Run: Start -> Git -> Git Bash
2. Type "cd x264-src"
3. Type "git pull origin"
4. Type "git log > Changelog.txt"
5. Type "git2rev.exe Changelog.txt"