summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser_about_handler.h
diff options
context:
space:
mode:
authorjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-04 07:49:14 +0000
committerjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-04 07:49:14 +0000
commit526d4500af3ff9bde66ce560e6e4b37418eb2a89 (patch)
tree9763b4d54e437d24d369194f5370fdd8c4d25ed5 /chrome/browser/browser_about_handler.h
parentfb6ce9a0cbf90c88f5820f1cc0dc2a9c091c80ee (diff)
downloadchromium_src-526d4500af3ff9bde66ce560e6e4b37418eb2a89.zip
chromium_src-526d4500af3ff9bde66ce560e6e4b37418eb2a89.tar.gz
chromium_src-526d4500af3ff9bde66ce560e6e4b37418eb2a89.tar.bz2
A brief test of whether we can safely disable ipv6. Will rollback asap.
Having had trouble with a probe based disabling of ipv6, I wanted to understand if globally disabling IPv6 is problematic. I'll roll-back this chance as soon as the build-bots begin to test it. tbr=wtc Review URL: http://codereview.chromium.org/573004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38085 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser_about_handler.h')
0 files changed, 0 insertions, 0 deletions