On Tue, Oct 20, 2009 at 1:25 PM, Jeremy Orlow wrote:
> On Tue, Oct 20, 2009 at 10:19 AM, David Levin wrote:
>
>> That sounds like a reasonable policy.
>
>
> Hmm...I thought this was the policy. I guess not? :-)
>
>
>> There is the current idea of figuring out something about the crash before
>
What do you mean by "that"? Updating the doc?
Btw, the original reason why I asked was that I wanted to confirm we all
agreed with this policy. I guess it sounds like everyone does and the only
question is making sure everyone starts following it?
J
On Tue, Oct 20, 2009 at 11:28 AM, Dimitri Gla
Yaar and I discussed making changes to that effect last week, he's
working on that.
:DG<
On Tue, Oct 20, 2009 at 10:33 AM, David Levin wrote:
> If it isn't written
> here http://dev.chromium.org/developers/how-tos/webkit-merge-1, then (imo)
> it isn't policy for gardener. :) Given that not ever
If it isn't written here
http://dev.chromium.org/developers/how-tos/webkit-merge-1, then (imo) it
isn't policy for gardener. :) Given that not everyone is in the same place,
if it isn't written in the standard place, how will folks know?
Even then, if you add something new, it would be nice to tell
On Tue, Oct 20, 2009 at 10:19 AM, David Levin wrote:
> That sounds like a reasonable policy.
Hmm...I thought this was the policy. I guess not? :-)
> There is the current idea of figuring out something about the crash before
> filing a bug, which clashes with this idea.
> What text would you
