how to map from position # to a version

743 views
Skip to first unread message

Guo-wei Shieh

unread,
Jan 13, 2015, 12:45:45 PM1/13/15
to chromium-dev
Hi,

https://omahaproxy.appspot.com/ tells me the mapping from version to position. Is there a reverse lookup?

Thanks,
Guowei

Bartosz Fabianowski

unread,
Jan 13, 2015, 12:51:33 PM1/13/15
to guo...@chromium.org, chromium-dev
https://chromium.googlesource.com/chromium/src/+/$REVISION/chrome/VERSION will
tell you what version a CL was committed to.

- Bartosz

Rob Wu

unread,
Jan 14, 2015, 11:36:53 AM1/14/15
to bar...@google.com, guo...@chromium.org, chromium-dev
And how about Blink revision -> Chrome version, or even Blink revision -> Chrome revision?
I currently look at http://blink.lc/chromium/log/?qt=grep&q=third_party%2FWebKit (in the past: http://blink.lc/chromium/log/?qt=grep&q=blink+roll) to find the commit position in Chrome, and then chrome/VERSION to find the Chrome version. Are there any better ways?

Kind regards,
 Rob
 https://robwu.nl

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

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

Guo-wei Shieh

unread,
Jan 14, 2015, 12:36:14 PM1/14/15
to Rob Wu, bar...@google.com, chromium-dev
Also, the VERSION doesn't seem to contain the full version string. It only has, for example, 39.0.2217.0. The last digit change is not reflected in version file. 

In addition to this, since the check in title only contains 2217, it becomes a task itself to make 2217 to M39... Or is there any easy way I missed? 

Stefan Zager

unread,
Jan 14, 2015, 12:38:22 PM1/14/15
to r...@robwu.nl, bar...@google.com, guo...@chromium.org, chromium-dev
On Wed Jan 14 2015 at 8:36:38 AM Rob Wu <r...@robwu.nl> wrote:
And how about Blink revision -> Chrome version, or even Blink revision -> Chrome revision?
I currently look at http://blink.lc/chromium/log/?qt=grep&q=third_party%2FWebKit (in the past: http://blink.lc/chromium/log/?qt=grep&q=blink+roll) to find the commit position in Chrome, and then chrome/VERSION to find the Chrome version. Are there any better ways?

*sigh*

No.

There are other ways, but none of them are better.  Hopefully, this becomes a moot point "soon", when we merge the chromium and blink repositories.

Bernhard Bauer

unread,
Jan 15, 2015, 4:50:37 AM1/15/15
to guo...@chromium.org, Rob Wu, bar...@google.com, chromium-dev
On Wed Jan 14 2015 at 5:36:06 PM Guo-wei Shieh <guo...@chromium.org> wrote:
Also, the VERSION doesn't seem to contain the full version string. It only has, for example, 39.0.2217.0. The last digit change is not reflected in version file. 

Trunk always has a PATCH version of 0. Larger numbers than that are used for branches, as a rough indication of how long that branch has existed.
 
In addition to this, since the check in title only contains 2217, it becomes a task itself to make 2217 to M39... Or is there any easy way I missed? 

MAJOR in chrome/VERSION?

Bernhard.
 
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
Reply all
Reply to author
Forward
0 new messages