From: Jay Soffian <jaysoffian@gmail.com>
To: Will Palmer <wmpalmer@gmail.com>
Cc: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
git@vger.kernel.org, jnareb@gmail.com, chriscool@tuxfamily.org,
pasky@ucw.cz
Subject: Re: [PATCHv2] git-web--browse: Add support for google chrome
Date: Wed, 19 May 2010 09:32:59 -0400 [thread overview]
Message-ID: <AANLkTikxis7BU-OGi76MzjN_JuOwmGNhDXYmZ1_bgMTl@mail.gmail.com> (raw)
In-Reply-To: <1274265104.2121.7.camel@wpalmer.simply-domain>
On Wed, May 19, 2010 at 6:31 AM, Will Palmer <wmpalmer@gmail.com> wrote:
> perhaps this has already been discussed, but aren't "chrome" and
> "chromium" two different browsers? (based on the same code, sure, but
> different releases which are often installed separately, all the same)
Correct. The chromium browser is 100% open-source. You can compile it
yourself or download a continuous build of it from the chromium trunk
(the Chromium project uses subversion for
chromium/chrome/chrome-frame, though interestingly uses git for
ChromiumOS). This is generally a developer release.
Google Chrome is a Google-branded version of the chromium browser. It
includes some non-opensource or restricted components (such as H.264
playback, Flash, Google design assets, etc), so you can't compile it
yourself. Rather you can only download binaries of various vintages
(dev, beta, stable). This is generally the consumer release.
j.
prev parent reply other threads:[~2010-05-19 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 9:51 [PATCHv4 GSoC] gitweb: Move static files into seperate subdirectory Pavan Kumar Sunkara
2010-05-19 9:51 ` [PATCHv2] git-web--browse: Add support for google chrome Pavan Kumar Sunkara
2010-05-19 10:06 ` Erik Faye-Lund
2010-05-19 10:31 ` Will Palmer
2010-05-19 13:32 ` Jay Soffian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikxis7BU-OGi76MzjN_JuOwmGNhDXYmZ1_bgMTl@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=pasky@ucw.cz \
--cc=pavan.sss1991@gmail.com \
--cc=wmpalmer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).