[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread David Levin
This fellow has done a good job of highlighting improvements to WebKit on an
on going basis:
  http://hanblog.info/blog/category/WebKit
Of course, not everything mentioned in there is in available just because
we're at ToT.  (Some things are behind ifdef's etc.)


On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:


 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the 154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 

 


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



[chromium-dev] Re: Stabilization Effort Daily Report

2009-01-06 Thread Evan Martin

On Mon, Jan 5, 2009 at 10:49 PM, Jon j...@chromium.org wrote:
 The Layout Tests class went well.  We are going to record it next week so
 people can watch it on demand.  Eric's slides are at
 http://www.corp.google.com/~ericroman/layout/   I appreciate the enthusiasm!

This isn't world-readable.  Perhaps we should set up webspace on
chromium.org for hosting these sorts of things?  Dimitri's webkit
merge tracker page would also be useful.

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



[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread Linus Upson

Do you also want a list of chrome specific non-webkit goodies like the
new network stack?

Linus


On Tue, Jan 6, 2009 at 1:44 AM, David Levin le...@google.com wrote:
 This fellow has done a good job of highlighting improvements to WebKit on an
 on going basis:
   http://hanblog.info/blog/category/WebKit
 Of course, not everything mentioned in there is in available just because
 we're at ToT.  (Some things are behind ifdef's etc.)

 On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:

 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the
  154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 




 


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



[chromium-dev] Re: Has your computer melted?

2009-01-06 Thread Marc-Antoine Ruel

I started seeing a slew of:

98glue.lib(autofill_form.obj) : fatal error LNK1318: Unexpected PDB
error; RPC (23) '(0x06BA)'

26...\xmemory(155) : error C2471: cannot update program database
'c:\b\slave\try-win32-2\build\src\chrome\debug\obj\plugin_tests\vc80.pdb'
26...\xmemory(155) : error C2471: cannot update program database '??? '

and other neat errors like that on the try slaves. I don't know why
but it doesn't seem to happen on the continuous build slaves. Maybe
related to IB?

Maybe we'll need to revert and folks can enable it locally.

On Mon, Jan 5, 2009 at 10:50 PM, Mohamed Mansour
m0.interact...@gmail.com wrote:
 Awesome Brett!
 My Quad Core processor is using all the 4 CPU :) 94% constant :x Mine took
 20minutes to build from scratch, big improvement! I was doing many other
 stuff at the same time, Java (Eclipse), C# Visual Studio, browsing.
 Awesome Improvement, thanks! No need to wait 40 minutes :)

 On Mon, Jan 5, 2009 at 7:32 PM, Brett Wilson bre...@chromium.org wrote:

 I just checked in a change to use /MP for all compiles, which is a
 secret undocumented flag that does parallel compiles within each
 project.

 Please let me know of your computer melts or becomes unusable during a
 compile. It should more efficiently use all of your CPUs when doing
 regular Visual Studio builds (it will have no effect on
 IncrediBuilds). You can remove it from essential.vsprops if it's
 causing problems.

 We tested on Carlos' 2-processor system and it pegged the CPU more,
 although it's not clear if it's a lot faster than before. On my
 4-processor system, a build of just chrome_exe and all of it's
 dependencies went from 25 to 16 minutes after using this flag. So if
 you hate IncrediBuild, life might actually be tolerable without it for
 fast systems.

 Brett




 


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



[chromium-dev] Re: Has your computer melted?

2009-01-06 Thread Mohamed Mansour
I got those fatal error LNK. That happens if:

   - When I stop the build in the middle.
   - When I code while building

I had to just clean that project Build  Clean project, and it works.

On Tue, Jan 6, 2009 at 2:22 PM, Marc-Antoine Ruel mar...@chromium.orgwrote:


 I started seeing a slew of:

 98glue.lib(autofill_form.obj) : fatal error LNK1318: Unexpected PDB
 error; RPC (23) '(0x06BA)'

 26...\xmemory(155) : error C2471: cannot update program database
 'c:\b\slave\try-win32-2\build\src\chrome\debug\obj\plugin_tests\vc80.pdb'
 26...\xmemory(155) : error C2471: cannot update program database '??? '

 and other neat errors like that on the try slaves. I don't know why
 but it doesn't seem to happen on the continuous build slaves. Maybe
 related to IB?

 Maybe we'll need to revert and folks can enable it locally.

 On Mon, Jan 5, 2009 at 10:50 PM, Mohamed Mansour
 m0.interact...@gmail.com wrote:
  Awesome Brett!
  My Quad Core processor is using all the 4 CPU :) 94% constant :x Mine
 took
  20minutes to build from scratch, big improvement! I was doing many other
  stuff at the same time, Java (Eclipse), C# Visual Studio, browsing.
  Awesome Improvement, thanks! No need to wait 40 minutes :)
 
  On Mon, Jan 5, 2009 at 7:32 PM, Brett Wilson bre...@chromium.org
 wrote:
 
  I just checked in a change to use /MP for all compiles, which is a
  secret undocumented flag that does parallel compiles within each
  project.
 
  Please let me know of your computer melts or becomes unusable during a
  compile. It should more efficiently use all of your CPUs when doing
  regular Visual Studio builds (it will have no effect on
  IncrediBuilds). You can remove it from essential.vsprops if it's
  causing problems.
 
  We tested on Carlos' 2-processor system and it pegged the CPU more,
  although it's not clear if it's a lot faster than before. On my
  4-processor system, a build of just chrome_exe and all of it's
  dependencies went from 25 to 16 minutes after using this flag. So if
  you hate IncrediBuild, life might actually be tolerable without it for
  fast systems.
 
  Brett
 
 
 
 
  
 

 


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



[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread e. roman

While not new to WebKit, Chromium's port now implements more of the
base features.

For example, brettw recently added support for stroked/filled text,
and transformed form controls.

Example: http://webkit.org/blog/85/introducing-text-stroke/

http://codereview.chromium.org/8615
http://codereview.chromium.org/9008

On Tue, Jan 6, 2009 at 9:09 AM, Linus Upson li...@google.com wrote:

 Do you also want a list of chrome specific non-webkit goodies like the
 new network stack?

 Linus


 On Tue, Jan 6, 2009 at 1:44 AM, David Levin le...@google.com wrote:
 This fellow has done a good job of highlighting improvements to WebKit on an
 on going basis:
   http://hanblog.info/blog/category/WebKit
 Of course, not everything mentioned in there is in available just because
 we're at ToT.  (Some things are behind ifdef's etc.)

 On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:

 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the
  154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 




 


 


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



[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread Evan Martin

On Tue, Jan 6, 2009 at 12:17 PM, e. roman ero...@chromium.org wrote:

 While not new to WebKit, Chromium's port now implements more of the
 base features.

 For example, brettw recently added support for stroked/filled text,
 and transformed form controls.

 Example: http://webkit.org/blog/85/introducing-text-stroke/

Though it seems the second example on that page doesn't work (Red
stroked text with a hollow interior and a black stroked shadow.) ...


 http://codereview.chromium.org/8615
 http://codereview.chromium.org/9008

 On Tue, Jan 6, 2009 at 9:09 AM, Linus Upson li...@google.com wrote:

 Do you also want a list of chrome specific non-webkit goodies like the
 new network stack?

 Linus


 On Tue, Jan 6, 2009 at 1:44 AM, David Levin le...@google.com wrote:
 This fellow has done a good job of highlighting improvements to WebKit on an
 on going basis:
   http://hanblog.info/blog/category/WebKit
 Of course, not everything mentioned in there is in available just because
 we're at ToT.  (Some things are behind ifdef's etc.)

 On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:

 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the
  154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 




 


 


 


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



[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread e. roman

On Tue, Jan 6, 2009 at 12:26 PM, Evan Martin e...@chromium.org wrote:

 On Tue, Jan 6, 2009 at 12:17 PM, e. roman ero...@chromium.org wrote:

 While not new to WebKit, Chromium's port now implements more of the
 base features.

 For example, brettw recently added support for stroked/filled text,
 and transformed form controls.

 Example: http://webkit.org/blog/85/introducing-text-stroke/

 Though it seems the second example on that page doesn't work (Red
 stroked text with a hollow interior and a black stroked shadow.) ...

Yeah, there are some bugs (scrolling messes up the shadows too).

Probably this: http://code.google.com/p/chromium/issues/detail?id=2982



 http://codereview.chromium.org/8615
 http://codereview.chromium.org/9008

 On Tue, Jan 6, 2009 at 9:09 AM, Linus Upson li...@google.com wrote:

 Do you also want a list of chrome specific non-webkit goodies like the
 new network stack?

 Linus


 On Tue, Jan 6, 2009 at 1:44 AM, David Levin le...@google.com wrote:
 This fellow has done a good job of highlighting improvements to WebKit on 
 an
 on going basis:
   http://hanblog.info/blog/category/WebKit
 Of course, not everything mentioned in there is in available just because
 we're at ToT.  (Some things are behind ifdef's etc.)

 On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:

 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the
  154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 




 


 


 


 


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



[chromium-dev] Re: What WebKit goodies do we get in 155?

2009-01-06 Thread Linus Upson

Should we mention that chrome scores 100/100 on Acid 3 (but actually
fails to render correctly)?

Linus


On Tue, Jan 6, 2009 at 12:37 PM, e. roman ero...@chromium.org wrote:

 On Tue, Jan 6, 2009 at 12:35 PM, e. roman ero...@chromium.org wrote:
 On Tue, Jan 6, 2009 at 12:26 PM, Evan Martin e...@chromium.org wrote:

 On Tue, Jan 6, 2009 at 12:17 PM, e. roman ero...@chromium.org wrote:

 While not new to WebKit, Chromium's port now implements more of the
 base features.

 For example, brettw recently added support for stroked/filled text,
 and transformed form controls.

 Example: http://webkit.org/blog/85/introducing-text-stroke/

 Though it seems the second example on that page doesn't work (Red
 stroked text with a hollow interior and a black stroked shadow.) ...

 Yeah, there are some bugs (scrolling messes up the shadows too).

 Probably this: http://code.google.com/p/chromium/issues/detail?id=2982

 Actually, meant to paste this bug number as it includes the repro.

 http://code.google.com/p/chromium/issues/detail?id=5925




 http://codereview.chromium.org/8615
 http://codereview.chromium.org/9008

 On Tue, Jan 6, 2009 at 9:09 AM, Linus Upson li...@google.com wrote:

 Do you also want a list of chrome specific non-webkit goodies like the
 new network stack?

 Linus


 On Tue, Jan 6, 2009 at 1:44 AM, David Levin le...@google.com wrote:
 This fellow has done a good job of highlighting improvements to WebKit 
 on an
 on going basis:
   http://hanblog.info/blog/category/WebKit
 Of course, not everything mentioned in there is in available just because
 we're at ToT.  (Some things are behind ifdef's etc.)

 On Mon, Jan 5, 2009 at 11:06 PM, Adam Barth aba...@chromium.org wrote:

 If 155 is coming off of trunk, it has postMessage(), which is exciting
 for us security wonks.

 Adam


 On Mon, Jan 5, 2009 at 9:30 PM, Mark Larson (Google) m...@chromium.org
 wrote:
  I'm working on release notes for 155. The big addition in 155 (vs the
  154
  code we've been releasing) is the WebKit update.
  What have we gained since we started merging to WebKit's trunk?
  So far, I've got
-- full page zoom
-- autoscroll
-- CSS gradients
-- CSS canvas drawing
-- (partly) CSS masks
-- (partly?) CSS reflections
  Can you think of other features worth noting in release notes?
  Thanks,
  Mark
  
 




 


 


 


 



 


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



[chromium-dev] Re: Stabilization Effort Daily Report

2009-01-06 Thread Jon
I am going to find a way to post Eric's stuff.  It would be great to have a
world visible web server that we can use to publish these internal reports.
 So far I have been using a script to update the SVN repository of the wiki
on code.google.com which is not very satisfying.
Jon

On Tue, Jan 6, 2009 at 8:59 AM, Evan Martin e...@chromium.org wrote:


 On Mon, Jan 5, 2009 at 10:49 PM, Jon j...@chromium.org wrote:
  The Layout Tests class went well.  We are going to record it next week so
  people can watch it on demand.  Eric's slides are at
  http://www.corp.google.com/~ericroman/layout/   I appreciate the
 enthusiasm!

 This isn't world-readable.  Perhaps we should set up webspace on
 chromium.org for hosting these sorts of things?  Dimitri's webkit
 merge tracker page would also be useful.

 


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



[chromium-dev] Re: HTTP BASIC/DIGEST BUG - Has it been fixed yet?

2009-01-06 Thread Jon
The builds from the trunk, which include this fix, will be coming soon to
the dev channel.  You can immediately try the latest builds at
http://build.chromium.org/buildbot/continuous/LATEST/ although these builds
are bleeding edge.
Information about joining the dev channel is at
http://dev.chromium.org/getting-involved/dev-channel/

Watch for news about the dev and beta channels this week on our official
blog at http://blog.chromium.org/

Jon

On Mon, Jan 5, 2009 at 1:05 PM, Wan-Teh Chang w...@google.com wrote:


 On Mon, Jan 5, 2009 at 12:28 PM, Evan Martin e...@chromium.org wrote:
 
  It would help if you link to the bug in the bug tracker.
 
  I believe this message is in reference to
   http://code.google.com/p/chromium/issues/detail?id=1629
  which has been marked fixed.

 This bug has been fixed on the trunk of the Chromium source tree.
 But the fix isn't in the latest Google Chrome release yet because
 it is based on a branch created in November.  We didn't backport
 the bug fix to the official branch because it's a big patch so there's
 a risk that we may introduce other bugs when we adapt it for the
 official branch, which uses a completely different HTTP stack.

 Hopefully the fix will appear in a Dev Channel release as part of
 our new HTTP stack very soon.

 Note: the bug is not that Chromium doesn't support HTTP BASIC
 and DIGEST authentication.  The bug is that Chromium will only
 send a HTTP Authorization header after receiving a 401 Authorization
 Required response to the first attempt of the request.

 Wan-Teh Chang

 


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



[chromium-dev] Re: test_shell and fonts

2009-01-06 Thread Adam Langley

On Tue, Jan 6, 2009 at 12:57 PM, Paweł Hajdan Jr.
phajdan...@chromium.org wrote:
 We start to have few users building Chromium in distributions other
 than Ubuntu, and the fonts layout tends to be different. On Gentoo
 which I run I had to make compatibility symlinks, which is not a big
 deal, but may be bigger obstacle for people having trouble just
 building it.

The fontconfig stuff is there to make things more hermetic, so that
differences in development platforms don't affect layout test results.
However, we already have a method of resolving fonts by name -
fontconfig. One could well imagine querying fontconfig for the
locations of the fontfiles by font name before resetting the config to
our hermetic version. I think that would be the correct solution if it
becomes a problem.


AGL

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



[chromium-dev] Re: test_shell and fonts

2009-01-06 Thread James Vega
2009/1/6 Evan Martin e...@chromium.org:
 On Tue, Jan 6, 2009 at 12:57 PM, Paweł Hajdan Jr.
 phajdan...@chromium.org wrote:
 I thought about bundling required fonts with the test_shell. I'm not
 sure about the licensing issues, but this would probably solve these
 technical problems. These fonts shouldn't change etc... What do you
 think?

 Some other ideas:
  - always pull fonts from a resources directory within test_shell, and
 require people to fix symlinks from that directory themselves (can we
 check in symlinks in svn?)
  - use a fontconfig file rather than the hard-coded list of paths and
 let people override it
  - use a command-line flag for the paths to search for fonts?  ugh, I
 hope that's not the best option.

 - Use RedHat's Liberation fonts[0]

Using fontconfig (as agl suggests) solves the general problem, but not
relying on restricted fonts is a benefit.

[0] - http://www.redhat.com/promo/fonts/

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



[chromium-dev] Re: test_shell and fonts

2009-01-06 Thread Evan Martin

On Tue, Jan 6, 2009 at 1:52 PM, James Vega vega.ja...@gmail.com wrote:
  - Use RedHat's Liberation fonts[0]

The project under discussion is test_shell, which we use to verify our
font metrics match those of Windows, so we must use the same fonts.
For an actual browser we'll surely use whichever fonts are on the
user's system.

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



[chromium-dev] Re: Has your computer melted?

2009-01-06 Thread Brett Wilson

On Jan 5, 4:32 pm, Brett Wilson bre...@chromium.org wrote:
 I just checked in a change to use /MP for all compiles, which is a
 secret undocumented flag that does parallel compiles within each
 project.

 Please let me know of your computer melts or becomes unusable during a
 compile. It should more efficiently use all of your CPUs when doing
 regular Visual Studio builds (it will have no effect on
 IncrediBuilds). You can remove it from essential.vsprops if it's
 causing problems.

 We tested on Carlos' 2-processor system and it pegged the CPU more,
 although it's not clear if it's a lot faster than before. On my
 4-processor system, a build of just chrome_exe and all of it's
 dependencies went from 25 to 16 minutes after using this flag. So if
 you hate IncrediBuild, life might actually be tolerable without it for
 fast systems.

This was backed out earlier today due to weird errors, especially with
regard to linking and symbols. Some people have also reported that
Visual Studio can think everything is out of date and rebuilds when
it's not necessary.

If you would like to keep trying this change out, do this locally:
http://chrome-svn/viewvc/chrome/trunk/src/build/internal/essential.vsprops?r1=7533r2=7573
and restart Visual Studio.

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



[chromium-dev] Re: New Wiki Page for LinuxBuildInstructions

2009-01-06 Thread Evan Martin

I'm sorry I didn't comment earlier, but I was away for the holidays.

Thanks for writing the pages.  I've overwritten the previous build
instructions with your new LinuxBuildInstructionsMainPage and fixed up
the English a bit.

To anyone on chromium-dev: the wiki is editable by anyone, so please
go ahead and fix mistakes you see.  It's easy enough for us to revert
mistakes.

In particular, I notice there are two different places
(LinuxBuildInstructionsPrerequisites and
LinuxOpenSuseBuildInstructions) that have differing information on
OpenSUSE.  I don't know anything about it, so if anyone on this list
wants to merge them, please do it.

On Wed, Dec 24, 2008 at 9:51 AM, skana...@gmail.com skana...@gmail.com wrote:

 I wrote a new version of this page:
  http://code.google.com/p/chromium/wiki/LinuxBuildInstructions

 The Goal is to better describe the process.

 The work done is:

 1) Simplify the previous Page, by splitting in 2 pages (MAIN and
 PREREQUISITES):
   http://code.google.com/p/chromium/wiki/LinuxBuildInstructionsMainPage
   http://code.google.com/p/chromium/wiki/LinuxBuildInstructionsPrerequisites

 2) Add link more link to other wiki page

 I propose to delete the previous page and use the new ones.
 Any comments?

 


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