Well, bear in mind that the revision number can be misleading since it only reflects the correct state of the official build at the time of a branch. As soon as we pull in fixes from the trunk into the official branch then the revision number gets updated to tip-of-tree build revision number, which would indicate the official branch is at tip of tree when in fact it does not contain all the fixes from tip-of-tree.
On Fri, Sep 26, 2008 at 01:12, Darin Fisher <[EMAIL PROTECTED]> wrote: > Additionally, if you load "about:version" in Chrome, it'll show you the > subversion revision number. That indicates the exact revision of the > chrome_official_branch used to generate the build. > -Darin > > > On Thu, Sep 25, 2008 at 5:47 PM, Nicolas Sylvain <[EMAIL PROTECTED]>wrote: > >> >> It does not really match any Chromium build directly. >> >> We branched the code from build 2458, then we tested it, and applied >> some bug fixes to it, and released it as 153.1. >> >> You can see the official build process by looking at the changes in >> the official branch : >> http://src.chromium.org/viewvc/chrome/branches/chrome_official_branch/src/ >> >> Nicolas >> >> On 9/25/08, Digital Boy <[EMAIL PROTECTED]> wrote: >> > >> > Can anyone tell me which build of Chromium the latest Chrome dev >> > release (0.2.153.1) correlates to? >> > >> > >> > >> > Thank you! >> > > >> > >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
