./www/chromium [Chromium browser]
[+] Add this package to your ports tracker

[ CVSweb ] [ Homepage ] [ RSS feed ]

Version: 72.0.3626.121, Package name: chromium-72.0.3626.121
Maintained by: Robert Nagy
Master sites:
Flavors (export FLAVOR=xyz, setenv FLAVOR xyz):
  • debug
  • component
Description
Chromium is an open-source browser project that aims
to build a safer, faster, and more stable way for all
Internet users to experience the web.


Filesize: 670332.285 KB
Version History (View Complete History)
  • (2019-03-03) Updated to version: chromium-72.0.3626.121
  • (2019-02-22) Updated to version: chromium-72.0.3626.119
  • (2019-02-14) Updated to version: chromium-72.0.3626.109
  • (2019-02-08) Updated to version: chromium-72.0.3626.96
  • (2019-02-06) Updated to version: chromium-72.0.3626.81
  • (2018-12-15) Updated to version: chromium-71.0.3578.98
  • (2018-12-07) Updated to version: chromium-71.0.3578.80
  • (2018-11-21) Updated to version: chromium-70.0.3538.110
  • (2018-11-15) Updated to version: chromium-70.0.3538.102
  • (2018-11-04) Updated to version: chromium-70.0.3538.77
[show/hide] View available PLISTS (Can be a lot of data)

CVS Commit History:

   2019-03-19 02:48:24 by Robert Nagy | Files touched by this commit (5)
Log message:
minimize the v8 javascript engine memory footprint as much as possible
to not eat up all the memory with sites using lots of javascript
   2019-03-19 02:48:24 by Robert Nagy | Files touched by this commit (5)
Log message:
minimize the v8 javascript engine memory footprint as much as possible
to not eat up all the memory with sites using lots of javascript
   2019-03-19 02:48:24 by Robert Nagy | Files touched by this commit (5)
Log message:
minimize the v8 javascript engine memory footprint as much as possible
to not eat up all the memory with sites using lots of javascript
   2019-03-19 02:48:24 by Robert Nagy | Files touched by this commit (5)
Log message:
minimize the v8 javascript engine memory footprint as much as possible
to not eat up all the memory with sites using lots of javascript
   2019-03-19 02:48:24 by Robert Nagy | Files touched by this commit (5)
Log message:
minimize the v8 javascript engine memory footprint as much as possible
to not eat up all the memory with sites using lots of javascript
   2019-03-17 03:47:01 by Robert Nagy | Files touched by this commit (2)
Log message:
add getpw pledge to the main process because when using cups, there will
be getpnam(3) calls by the cups library
   2019-03-17 03:47:01 by Robert Nagy | Files touched by this commit (2)
Log message:
add getpw pledge to the main process because when using cups, there will
be getpnam(3) calls by the cups library
   2019-03-11 14:19:42 by Robert Nagy | Files touched by this commit (2)
Log message:
ignore ENOENT up until the last element of the path when doing mkdir(2)
on unveil(2)'d directory trees ... essentially the same modification that
went into gtk+3
this allows us to remove some hacks from unveil(2)
   2019-03-11 14:19:42 by Robert Nagy | Files touched by this commit (2)
Log message:
ignore ENOENT up until the last element of the path when doing mkdir(2)
on unveil(2)'d directory trees ... essentially the same modification that
went into gtk+3
this allows us to remove some hacks from unveil(2)
   2019-03-03 02:45:28 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.121
   2019-03-03 02:45:28 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.121
   2019-02-26 14:31:36 by Robert Nagy | Files touched by this commit (3)
Log message:
do not try to raise limits on-the-fly to avoid breaking the pledge(2)
   2019-02-26 14:31:36 by Robert Nagy | Files touched by this commit (3)
Log message:
do not try to raise limits on-the-fly to avoid breaking the pledge(2)
   2019-02-26 14:31:36 by Robert Nagy | Files touched by this commit (3)
Log message:
do not try to raise limits on-the-fly to avoid breaking the pledge(2)
   2019-02-22 09:48:13 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.119
   2019-02-22 09:48:13 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.119
   2019-02-19 08:04:54 by Robert Nagy | Files touched by this commit (1)
Log message:
be nice and create ~/Downloads if its not there
   2019-02-19 07:57:53 by Robert Nagy | Files touched by this commit (5)
Log message:
Make sure to always default to the Downloads directory in case a file
dialog is opened and unveil(2) is used.
This fixes the issue when another program not using unveil(2) changes
the last used path of the file dialog and then the file dialog opened
by chrome will get stuck inside a non-existent directory.
To make sure that the ~/Downloads XDG directory is always available
for glib to pick up, the chrome wrapper script will check if the
~/.config/user-dirs.dirs does not exist and create it with one entry
configured: XDG_DOWNLOAD_DIR="$HOME/Downloads"
   2019-02-19 07:57:53 by Robert Nagy | Files touched by this commit (5)
Log message:
Make sure to always default to the Downloads directory in case a file
dialog is opened and unveil(2) is used.
This fixes the issue when another program not using unveil(2) changes
the last used path of the file dialog and then the file dialog opened
by chrome will get stuck inside a non-existent directory.
To make sure that the ~/Downloads XDG directory is always available
for glib to pick up, the chrome wrapper script will check if the
~/.config/user-dirs.dirs does not exist and create it with one entry
configured: XDG_DOWNLOAD_DIR="$HOME/Downloads"
   2019-02-19 07:57:53 by Robert Nagy | Files touched by this commit (5)
Log message:
Make sure to always default to the Downloads directory in case a file
dialog is opened and unveil(2) is used.
This fixes the issue when another program not using unveil(2) changes
the last used path of the file dialog and then the file dialog opened
by chrome will get stuck inside a non-existent directory.
To make sure that the ~/Downloads XDG directory is always available
for glib to pick up, the chrome wrapper script will check if the
~/.config/user-dirs.dirs does not exist and create it with one entry
configured: XDG_DOWNLOAD_DIR="$HOME/Downloads"
   2019-02-19 07:57:53 by Robert Nagy | Files touched by this commit (5)
Log message:
Make sure to always default to the Downloads directory in case a file
dialog is opened and unveil(2) is used.
This fixes the issue when another program not using unveil(2) changes
the last used path of the file dialog and then the file dialog opened
by chrome will get stuck inside a non-existent directory.
To make sure that the ~/Downloads XDG directory is always available
for glib to pick up, the chrome wrapper script will check if the
~/.config/user-dirs.dirs does not exist and create it with one entry
configured: XDG_DOWNLOAD_DIR="$HOME/Downloads"
   2019-02-19 07:57:53 by Robert Nagy | Files touched by this commit (5)
Log message:
Make sure to always default to the Downloads directory in case a file
dialog is opened and unveil(2) is used.
This fixes the issue when another program not using unveil(2) changes
the last used path of the file dialog and then the file dialog opened
by chrome will get stuck inside a non-existent directory.
To make sure that the ~/Downloads XDG directory is always available
for glib to pick up, the chrome wrapper script will check if the
~/.config/user-dirs.dirs does not exist and create it with one entry
configured: XDG_DOWNLOAD_DIR="$HOME/Downloads"
   2019-02-14 09:14:27 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.109
   2019-02-14 09:14:27 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 72.0.3626.109
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-07 11:22:18 by Robert Nagy | Files touched by this commit (8)
Log message:
update to 72.0.3626.96
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-02-06 09:41:56 by Robert Nagy | Files touched by this commit (250)
Log message:
update to 72.0.3626.81
now chromium uses f'in java to use the closure compiler which
creates "better javascript" by parsing and converting all js
code into unreadable garbage. this feature is only enable on
amd64 because on i386 java randomly fails to allocate the needed
memory and on arm64 we do not have jdk yet. on these architectures,
we use the best method to create "better javascript", which is cat(1)
   2019-01-30 15:47:35 by Stuart Henderson | Files touched by this commit (2)
Log message:
set DPB_PROPERTIES+=lonesome on chromium/iridium for i386 (like is done
for firefox) in the hope that this will reduce build problems. these
ports often end up building together on a machine and they aren't coping
too well.
compiling some individual files is now bumping into my 75 minute DPB
stuck_timeout (possibly the llvm update took it over the edge) - raising
the timeout means that the other ports which occasionally hang during
compilation tie up a build slot for too long.
   2019-01-06 12:49:53 by Robert Nagy | Files touched by this commit (3)
Log message:
pre-create the .cache/chromium and .local/share/applications directories
so that unveil will not fail on them if they do not exist yet
   2019-01-06 12:49:53 by Robert Nagy | Files touched by this commit (3)
Log message:
pre-create the .cache/chromium and .local/share/applications directories
so that unveil will not fail on them if they do not exist yet
   2019-01-06 12:49:53 by Robert Nagy | Files touched by this commit (3)
Log message:
pre-create the .cache/chromium and .local/share/applications directories
so that unveil will not fail on them if they do not exist yet
   2019-01-04 06:25:08 by Robert Nagy | Files touched by this commit (4)
Log message:
remove error pledge because it is not needed and sync the sandbox code
with linux
   2019-01-04 06:25:08 by Robert Nagy | Files touched by this commit (4)
Log message:
remove error pledge because it is not needed and sync the sandbox code
with linux
   2019-01-04 06:25:08 by Robert Nagy | Files touched by this commit (4)
Log message:
remove error pledge because it is not needed and sync the sandbox code
with linux
   2019-01-04 06:25:08 by Robert Nagy | Files touched by this commit (4)
Log message:
remove error pledge because it is not needed and sync the sandbox code
with linux
   2018-12-25 10:32:43 by Robert Nagy | Files touched by this commit (3)
Log message:
lock down the unveils even more to avoid having access to the complete
~/.local and ~/.config directories and initialize NSS before unveil so
that the ~/.pki and the subdirectories can be created just in time
   2018-12-25 10:32:43 by Robert Nagy | Files touched by this commit (3)
Log message:
lock down the unveils even more to avoid having access to the complete
~/.local and ~/.config directories and initialize NSS before unveil so
that the ~/.pki and the subdirectories can be created just in time
   2018-12-25 10:32:43 by Robert Nagy | Files touched by this commit (3)
Log message:
lock down the unveils even more to avoid having access to the complete
~/.local and ~/.config directories and initialize NSS before unveil so
that the ~/.pki and the subdirectories can be created just in time
   2018-12-15 03:08:09 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 71.0.3578.98
   2018-12-15 03:08:09 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 71.0.3578.98
   2018-12-15 03:08:09 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 71.0.3578.98
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-07 04:07:35 by Robert Nagy | Files touched by this commit (225)
Log message:
update to 71.0.3578.80
   2018-12-04 02:55:08 by Robert Nagy | Files touched by this commit (6)
Log message:
fix theme handling by actually showing the necessary buttons in the settings
page
   2018-12-04 02:55:08 by Robert Nagy | Files touched by this commit (6)
Log message:
fix theme handling by actually showing the necessary buttons in the settings
page
   2018-12-04 02:55:08 by Robert Nagy | Files touched by this commit (6)
Log message:
fix theme handling by actually showing the necessary buttons in the settings
page
   2018-11-30 10:22:35 by Robert Nagy | Files touched by this commit (4)
Log message:
add unveil(2) for /usr/bin/lpr to make the system print dialog work when
using lpr for printing
   2018-11-30 10:22:35 by Robert Nagy | Files touched by this commit (4)
Log message:
add unveil(2) for /usr/bin/lpr to make the system print dialog work when
using lpr for printing
   2018-11-27 11:20:51 by Christian Weisgerber | Files touched by this commit (2)
Log message:
Allow text relocations on i386, caused by optimized non-PIC assembly in
the embedded copy of FFmpeg.  Chromium build test by sthen@,
looks good to robert@
   2018-11-20 12:09:41 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 70.0.3538.110
   2018-11-20 12:09:41 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 70.0.3538.110
   2018-11-20 12:09:41 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 70.0.3538.110
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-17 09:18:11 by Robert Nagy | Files touched by this commit (10)
Log message:
enable unveil(2) by default in chromium;
if you wish to disable it, please run chromium with the --disable-unveil flag
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-15 08:28:43 by Robert Nagy | Files touched by this commit (9)
Log message:
update to 70.0.3538.102
   2018-11-11 06:50:57 by Robert Nagy | Files touched by this commit (1)
Log message:
unbreak i386 build by defining explicit WebVector(size_t size) : data_(size) {}
for non 64-bit arches on OpenBSD as well
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-11-04 05:33:24 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 70.0.3538.77
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-27 00:36:18 by Robert Nagy | Files touched by this commit (19)
Log message:
add some missing openbsd ifdefs after the overhaul of the UI
   2018-09-23 06:49:26 by Stuart Henderson | Files touched by this commit (2)
Log message:
disable USE_LLD on i386, it still doesn't work there for these ports:
can't create dynamic relocation R_386_32 against local symbol in
readonly segment; recompile object files with -fPIC
   2018-09-20 04:28:17 by Robert Nagy | Files touched by this commit (1)
Log message:
set USE_LLD to Yes for chrome to shave at least 30 minutes of build time
   2018-09-20 02:43:54 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 69.0.3497.100 and enable jumbo build
To improve compilation times it is possible to use Jumbo builds,
in Chromium.
The idea is to merge many source files and compile them together.
Since a large portion of Chromium's code is in shared header files
that dramatically reduces the total amount of work needed.
fix an internal build dependency while here
   2018-09-20 02:43:54 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 69.0.3497.100 and enable jumbo build
To improve compilation times it is possible to use Jumbo builds,
in Chromium.
The idea is to merge many source files and compile them together.
Since a large portion of Chromium's code is in shared header files
that dramatically reduces the total amount of work needed.
fix an internal build dependency while here
   2018-09-20 02:43:54 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 69.0.3497.100 and enable jumbo build
To improve compilation times it is possible to use Jumbo builds,
in Chromium.
The idea is to merge many source files and compile them together.
Since a large portion of Chromium's code is in shared header files
that dramatically reduces the total amount of work needed.
fix an internal build dependency while here
   2018-09-20 02:43:54 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 69.0.3497.100 and enable jumbo build
To improve compilation times it is possible to use Jumbo builds,
in Chromium.
The idea is to merge many source files and compile them together.
Since a large portion of Chromium's code is in shared header files
that dramatically reduces the total amount of work needed.
fix an internal build dependency while here
   2018-09-18 06:51:44 by Marc Espie | Files touched by this commit (1)
Log message:
annotate the monster with parallel2.
dpb now has a special feature where parallel2 may be set to use even
more cores than parallel.
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-16 05:08:34 by Robert Nagy | Files touched by this commit (7)
Log message:
enable the new chromium UI on openbsd as well
   2018-09-14 08:56:18 by Robert Nagy | Files touched by this commit (1)
Log message:
fix the swiftshader PKG_ARG on aarch64
   2018-09-13 09:04:39 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 69.0.3497.92 and fix a missing dependency on e2fsprogs
   2018-09-13 09:04:39 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 69.0.3497.92 and fix a missing dependency on e2fsprogs
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 13:10:34 by Robert Nagy | Files touched by this commit (18)
Log message:
add support for arm64;
This is now possible due to the libcxx update and pmap changes in the kernel.
Since swiftshader is not supported on aarch64 (amd64), create a PFRAG to be
included on anything else besides arm64.
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-12 11:08:22 by Robert Nagy | Files touched by this commit (239)
Log message:
update to 69.0.3497.81
   2018-09-10 13:51:13 by Robert Nagy | Files touched by this commit (1)
Log message:
update-patches strikes again .. do not include my pobj path
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-09-04 01:20:43 by Robert Nagy | Files touched by this commit (8)
Log message:
remove more /sys and /proc access and add required unveil for /etc/machine-id
and some missing pledges for the main process
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-10 08:57:53 by Robert Nagy | Files touched by this commit (32)
Log message:
update to 68.0.3440.106 and include all the unveil configuration files
by default now, so there is no need to clone the git repository for that
   2018-08-05 06:47:21 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 68.0.3440.84
   2018-08-05 06:47:21 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 68.0.3440.84
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-30 09:28:28 by Robert Nagy | Files touched by this commit (207)
Log message:
update to 68.0.3440.75
   2018-07-25 04:42:05 by Robert Nagy | Files touched by this commit (1)
Log message:
remove bogous patch
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-07-25 00:53:36 by Robert Nagy | Files touched by this commit (44)
Log message:
Introduce unveil(2) support for chromium;
I am commiting this so that work can continue in tree because the diff
is starting to get really big. This commit includes several changes
required for unveil(2) described below:
- overhaul of the sandboxing code for pledge(2) to match what is being
done on other platforms
- avoid using /dev/urandom and switch to arc4random(3) or arc4random_buf(3)
- start using pledge(2) for the main browser process as well, disabled by
default for now as the list changes rapidly. The list of pledges are read
from the /etc/chromium/pledge.main file if available. When this is complete
the list of pledges will be hardcoded just as it is for the other process
types.
- add the --enable-unveil flag to use unveil(2) in all of the browser processes
by reading the list of unveil'd paths from files located in /etc/chromium,
e.g.: /etc/chromium/unveil.main or /etc/chromium/unveil.gpu.
These files are not included in the package by default as they are work in
progress. If you want to help please visit: https://github.com/rnagy/chromium
- if unveil(2) is used, chromium will not be able to access most of the filesystem
so for example if you would like to download or upload something, only the unveil'd
paths are going to be available, which is by default include ~/Downloads.
   2018-06-29 16:16:37 by Marc Espie | Files touched by this commit (950)
Log message:
@tag gtk-update-icon-cache
   2018-06-29 16:16:37 by Marc Espie | Files touched by this commit (950)
Log message:
@tag gtk-update-icon-cache
   2018-06-27 15:04:25 by Marc Espie | Files touched by this commit (1411)
Log message:
first tag: update-desktop-database
   2018-06-27 15:04:25 by Marc Espie | Files touched by this commit (1411)
Log message:
first tag: update-desktop-database
   2018-06-18 23:32:31 by Robert Nagy | Files touched by this commit (2)
Log message:
67.0.3396.87
   2018-06-18 23:32:31 by Robert Nagy | Files touched by this commit (2)
Log message:
67.0.3396.87
   2018-06-07 02:48:29 by Robert Nagy | Files touched by this commit (2)
Log message:
add tmppath pledge for the gpu process for DRI3
   2018-06-07 02:48:29 by Robert Nagy | Files touched by this commit (2)
Log message:
add tmppath pledge for the gpu process for DRI3
   2018-06-05 06:41:49 by Robert Nagy | Files touched by this commit (2)
Log message:
unbreak build by not hardcoding my pobj
   2018-06-05 06:41:49 by Robert Nagy | Files touched by this commit (2)
Log message:
unbreak build by not hardcoding my pobj
   2018-06-04 08:04:23 by Robert Nagy | Files touched by this commit (2)
Log message:
do not link to libatomic as we use clang
   2018-06-04 08:04:23 by Robert Nagy | Files touched by this commit (2)
Log message:
do not link to libatomic as we use clang
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-06-02 11:19:23 by Robert Nagy | Files touched by this commit (235)
Log message:
update to 67.0.3396.62
   2018-05-16 11:48:07 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 66.0.3359.181
   2018-05-16 11:48:07 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 66.0.3359.181
   2018-05-11 07:12:56 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 66.0.3359.170
   2018-05-11 07:12:56 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 66.0.3359.170
   2018-05-11 07:12:56 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 66.0.3359.170
   2018-05-11 07:12:56 by Robert Nagy | Files touched by this commit (4)
Log message:
update to 66.0.3359.170
   2018-04-27 08:47:00 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 66.0.3359.139 and remove unnecessary patch
   2018-04-27 08:47:00 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 66.0.3359.139 and remove unnecessary patch
   2018-04-27 08:47:00 by Robert Nagy | Files touched by this commit (3)
Log message:
update to 66.0.3359.139 and remove unnecessary patch
   2018-04-27 02:21:45 by Robert Nagy | Files touched by this commit (1)
Log message:
fix syntax erron in python script
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-26 13:41:38 by Robert Nagy | Files touched by this commit (11)
Log message:
add a flavor called component to allow chromium to be built as a non-static
binary to ease development
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-25 03:23:38 by Robert Nagy | Files touched by this commit (6)
Log message:
avoid hitting pledge aborts while running the task manager and
fix a multiple symbol definition
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-23 09:00:16 by Robert Nagy | Files touched by this commit (183)
Log message:
update to 66.0.3359.117
   2018-04-07 12:59:43 by Robert Nagy | Files touched by this commit (3)
Log message:
the utility process needs a sendfd pledge as well in case chrome is running
in complete process separation mode to be able to send back data to the
renderer, for printing to pdf files for example
   2018-04-07 12:59:43 by Robert Nagy | Files touched by this commit (3)
Log message:
the utility process needs a sendfd pledge as well in case chrome is running
in complete process separation mode to be able to send back data to the
renderer, for printing to pdf files for example
   2018-04-07 12:59:43 by Robert Nagy | Files touched by this commit (3)
Log message:
the utility process needs a sendfd pledge as well in case chrome is running
in complete process separation mode to be able to send back data to the
renderer, for printing to pdf files for example
   2018-03-21 13:58:17 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 65.0.3325.181
   2018-03-21 13:58:17 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 65.0.3325.181
   2018-03-15 03:31:23 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 65.0.3325.162
   2018-03-15 03:31:23 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 65.0.3325.162
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-03-12 07:48:34 by Robert Nagy | Files touched by this commit (191)
Log message:
update to 65.0.3325.146
   2018-02-26 00:50:49 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.186
   2018-02-26 00:50:49 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.186
   2018-02-14 05:15:44 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.167
   2018-02-14 05:15:44 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.167
   2018-02-02 10:16:29 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.140
   2018-02-02 10:16:29 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 64.0.3282.140
   2018-02-01 22:56:40 by Robert Nagy | Files touched by this commit (1)
Log message:
unbreak build by not hardcoding my pobj path
   2018-02-01 22:44:34 by Robert Nagy | Files touched by this commit (2)
Log message:
bump the v8 max code range size to 512M from 256M
   2018-02-01 22:44:34 by Robert Nagy | Files touched by this commit (2)
Log message:
bump the v8 max code range size to 512M from 256M
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-30 00:57:25 by Robert Nagy | Files touched by this commit (249)
Log message:
update to 64.0.3282.119
   2018-01-05 10:35:11 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 63.0.3239.132
   2018-01-05 10:35:11 by Robert Nagy | Files touched by this commit (2)
Log message:
update to 63.0.3239.132
   2017-12-24 17:17:32 by Robert Nagy | Files touched by this commit (10)
Log message:
Make Chromecast devices and casting work by doing several different things:
- the media router extension which handles chromecast is only enabled
on official Chrome builds so enable it on chromium as well
- our multicast implementation is a legacy one so patch it around
to make it work and use SO_REUSEADDR and SO_REUSEPORT on the socket
to make other clients able to bind to the same port and address so
that everything will work smoothly together and chromium will not
"block" the multicast ports
- enable a good amount of features that are used in the javascript extension
code that were only enabled for linux and used by the media router
extension
Everything works from youtube casting, desktop casting to browser tab casting.
The only thing that does not work is the actual initial setup of the chromecast
device because that requires connecting to the device's wifi network and the browser
cannot do that on OpenBSD so another device has to be used for that, but I guess
everyone has a smartphone nowadays :)
   2017-12-24 17:17:32 by Robert Nagy | Files touched by this commit (10)
Log message:
Make Chromecast devices and casting work by doing several different things:
- the media router extension which handles chromecast is only enabled
on official Chrome builds so enable it on chromi