How to find code commits between two chrome versions ?

1,391 views
Skip to first unread message

rbha...@nvidia.com

unread,
Nov 5, 2014, 4:47:14 AM11/5/14
to chromi...@chromium.org
Need some ways which gives list of commits between two chrome versions. This is useful for finding out fix or culprit commit which introduces regression.

Anthony Berent

unread,
Nov 5, 2014, 4:57:24 AM11/5/14
to rbha...@nvidia.com, chromi...@chromium.org
Does "git log a..b" do what you want, where a and b are either the commit hashes or branch or tag names?

Note that, if it is a large range, there are also a some scripts for bisecting the range in the tools directory. These also take into account Blink commits.

On Wed Nov 05 2014 at 9:47:28 AM <rbha...@nvidia.com> wrote:
Need some ways which gives list of commits between two chrome versions. This is useful for finding out fix or culprit commit which introduces regression.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

rbha...@nvidia.com

unread,
Nov 5, 2014, 5:19:38 AM11/5/14
to chromi...@chromium.org, rbha...@nvidia.com
need code commits between two chrome versions e.g commits in all repos of chrome between version 33 and 34.

Marc-Antoine Ruel

unread,
Nov 5, 2014, 8:07:40 AM11/5/14
to rbha...@nvidia.com, chromium-dev
$ git tag | grep '^33'
(lots of output)
$ git rev-parse 33.0.1750.76
ff70ea75b5170adc30d0ffe50dd405f230704d8b

I recommend looking at http://git-scm.com/documentation for more information.

Thanks,

M-A

--
M-A

Anthony Berent

unread,
Nov 5, 2014, 8:16:37 AM11/5/14
to mar...@chromium.org, rbha...@nvidia.com, chromium-dev
If you have builds of the versions you are looking at then I think that the "About Chrome" page will tell you the full tag name.

rbha...@nvidia.com

unread,
Nov 5, 2014, 8:47:06 AM11/5/14
to chromi...@chromium.org, mar...@chromium.org, rbha...@nvidia.com
I found below procedure to find out commits between two chrome builds

1) Go to http://src.chromium.org/viewvc/chrome/releases/
2) Find chrome version i.e chrome 34.0.1847.114 and open DEPS file
3) Find revision number of interested repository
 e.g.
 'src':
          '/branches/1847/src@259599'
  259599 is rev number.
4) Similarly find revision number for second chrome version
5) Go to http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog.html?url=/trunk/src&mode=html&range=SUCCESS_REV:FAILURE_REV
6) Enter both revision numbers and you will get all commits between these revisions.

Michael Moss

unread,
Nov 5, 2014, 11:04:45 AM11/5/14
to rbha...@nvidia.com, chromium-dev
On Wed, Nov 5, 2014 at 5:47 AM, <rbha...@nvidia.com> wrote:
I found below procedure to find out commits between two chrome builds
 
The simplest (web-based) option is probably to just use the "Change Log" tool at the bottom of http://omahaproxy.appspot.com/. Enter the two version numbers, click the button, then click the link it generates. You can also use it to get the corresponding Blink (WebKit) change log.
This is the old svn repo and is no longer appropriate now that chromium is in git (note that the newest version there is 2 months old).

Primiano Tucci

unread,
Nov 5, 2014, 2:29:59 PM11/5/14
to Michael Moss, rbha...@nvidia.com, chromium-dev
If you are only interested in commits in the main projects:

git fetch --tags
git log --oneline 33.0.1750.80..34.0.1847.90  (I took random branch numbers, i.e. 1750, 1847). You should look them into omahaproxy.appspot.com / about:version 

However, when you narrow to a single revision, you might want to deep dive into the subprojects, e.g., third_party/WebKit.
Reply all
Reply to author
Forward
0 new messages