On Sat, Mar 26, 2011 at 3:24 AM, Patrick Gansterer wrote:
> Hi,
>
> Sometimes folks commit changes without bug numbers. If those changes breaks
> things it's hard to find the correct context for the change.
> Can we make the bug number a requirement for a commit when it has a
> corresponding bug?
Am 26.03.2011 um 19:30 schrieb Brent Fulgham:
> I don't want to have a bug report for everything either, but I do agree that
> my failure to include it in the changelog for the FontPlatformData change was
> a stupid oversight.
>
> I'll make sure to avoid that mistake in the future!
I didn't wa
On Sat, Mar 26, 2011 at 10:41 AM, Darin Adler wrote:
> On Mar 26, 2011, at 3:24 AM, Patrick Gansterer wrote:
>
> > Sometimes folks commit changes without bug numbers. If those changes
> breaks things it's hard to find the correct context for the change.
> > Can we make the bug number a requiremen
> If you use webkit-patch everything just magically works (yay!!)
>
> --Oliver
>
I agree! And if people would use it on uploading patches to a bug report, we
wouldn't need a style-bot.
Dirk
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
htt
If you use webkit-patch everything just magically works (yay!!)
--Oliver
On Mar 26, 2011, at 11:30 AM, Brent Fulgham wrote:
>
> On Mar 26, 2011, at 10:41 AM, Darin Adler wrote:
>
>> On Mar 26, 2011, at 3:24 AM, Patrick Gansterer wrote:
>>
>>> Sometimes folks commit changes without bug numbers
On Mar 26, 2011, at 10:41 AM, Darin Adler wrote:
> On Mar 26, 2011, at 3:24 AM, Patrick Gansterer wrote:
>
>> Sometimes folks commit changes without bug numbers. If those changes breaks
>> things it's hard to find the correct context for the change.
>> Can we make the bug number a requirement f
On Mar 26, 2011, at 3:24 AM, Patrick Gansterer wrote:
> Sometimes folks commit changes without bug numbers. If those changes breaks
> things it's hard to find the correct context for the change.
> Can we make the bug number a requirement for a commit when it has a
> corresponding bug?
> IMHO it
Hi,
Sometimes folks commit changes without bug numbers. If those changes breaks
things it's hard to find the correct context for the change.
Can we make the bug number a requirement for a commit when it has a
corresponding bug?
IMHO it would be great if the style bot and the reviewer complain ab
I've just uploaded a patch for WebKit that provides event-oriented
parser for XML called XMLReader that is a variant of the behavior of
XMLHttpRequest but, instead of building a whole document DOM, it
delivers "XML Events" to an EventListener. The implementation has
very low memory consumption cha
9 matches
Mail list logo