o that bug is checked in. We try
> to
> > always include BUG=n in our checkins and then bug n will be updated
> > automatically.
> > You could also subscribe to the chromium-checkins group to monitor each
> > checkin that get submitted, but that seems like overkill for wha
sues/detail?id=19) which I see has been
chosen as a GSoC project, is there anywhere I can subscribe to in order to
ascertain how far through the implementation of that piece of work peeps
are, or is the GSoC process a bit of a black-box affair ?
-cj
On Sat, Jun 20, 2009 at 5:54 PM, Ciaran wrote:
for digging into this feature.
>
>
> On Sat, Jun 20, 2009 at 02:37, Ciaran wrote:
>
>>
>>
>> On Fri, Jun 19, 2009 at 6:47 PM, Evan Martin wrote:
>>
>>> I am not a lawyer, but that is the intent.
>>>
>>> (In some sense Google Chrome is
On Fri, Jun 19, 2009 at 6:47 PM, Evan Martin wrote:
> I am not a lawyer, but that is the intent.
>
> (In some sense Google Chrome is just a commercial consumer of the code
> base as well. As I understand it, contributors retain copyright on
> their contributions, so it's not even the case that G