[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Scott Hess
On Wed, Jul 22, 2009 at 2:57 PM, Mark Larson (Google) wrote: > On Wed, Jul 22, 2009 at 14:02, Peter Kasting wrote: >> On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: >>> >>> Here comes the bike shedding >> >> Yes, Evan already concluded that was where we were. >>> >>> RELEASE_NOTES= >> >> I

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Andrew Scherkus
Even though git-cl doesn't have presubmit checks per se, I do like how it forces your first line to <= 100 characters (rietveld limitation, I believe). gcl gets around this issue by truncating your description and adding an ellipsis. On Wed, Jul 22, 2009 at 2:52 PM, Darin Fisher wrote: > On Wed

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Darin Fisher
On Wed, Jul 22, 2009 at 2:02 PM, Peter Kasting wrote: > On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: > >> Here comes the bike shedding > > > Yes, Evan already concluded that was where we were. > > RELEASE_NOTES= >> > > I thought the conclusion was that people should just write better com

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Mark Larson (Google)
On Wed, Jul 22, 2009 at 14:02, Peter Kasting wrote: > On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: > >> Here comes the bike shedding > > > Yes, Evan already concluded that was where we were. > > RELEASE_NOTES= >> > > I thought the conclusion was that people should just write better commi

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Jeremy Orlow
On Wed, Jul 22, 2009 at 2:52 PM, Darin Fisher wrote: > On Wed, Jul 22, 2009 at 2:02 PM, Peter Kasting wrote: > >> On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: >> >>> Here comes the bike shedding >> >> >> Yes, Evan already concluded that was where we were. >> >> RELEASE_NOTES= >>> >> >> I

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Ojan Vafai
Bug filed: http://code.google.com/p/chromium/issues/detail?id=17471 On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: > Here comes the bike shedding...but what about this: > """ > > > BUG= > TEST= > RELEASE_NOTES= > """ > > I don't think any ALL CAPS TEXT at the top is going to make people pu

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Peter Kasting
On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow wrote: > Here comes the bike shedding Yes, Evan already concluded that was where we were. RELEASE_NOTES= > I thought the conclusion was that people should just write better commit messages? Maybe I'm wrong. I'd almost prefer: BUG= TEST= ..

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Jeremy Orlow
Here comes the bike shedding...but what about this: """ BUG= TEST= RELEASE_NOTES= """ I don't think any ALL CAPS TEXT at the top is going to make people put in better descriptions. If you want bug to be a url, it should use crbug.cominstead of the full string, but the convention so far has been

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Ojan Vafai
I'm OK with not having the function list. I can see the advantages of the webkit approach as it means that comments in the code don't get outdated. But, then it forces you to look at the changelog history of every line of code. Anyways, how about we prepopulate gcl/git-cl change with this text: DET

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Jeremy Orlow
On Wed, Jul 22, 2009 at 1:22 PM, Peter Kasting wrote: > On Wed, Jul 22, 2009 at 1:17 PM, Ojan Vafai wrote: > >> platform/graphics/chromium/FontPlatformDataLinux.cpp: >>>(WebCore::FontPlatformData::setHinting): (WebCore::FontPlatformData::setAntiAlias): (WebCore::FontP

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Evan Martin
>>> platform/graphics/chromium/FontPlatformDataLinux.cpp: >>> >>>   (WebCore::FontPlatformData::setHinting): >>>   (WebCore::FontPlatformData::setAntiAlias): >>>   (WebCore::FontPlatformData::setSubpixelGlyphs): >>>   (WebCore::FontPlatformData::setupPaint): Modified to do something super >>> spec

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Peter Kasting
On Wed, Jul 22, 2009 at 1:17 PM, Ojan Vafai wrote: > >>> platform/graphics/chromium/FontPlatformDataLinux.cpp: >>> >> (WebCore::FontPlatformData::setHinting): >>> (WebCore::FontPlatformData::setAntiAlias): >>> (WebCore::FontPlatformData::setSubpixelGlyphs): >>> (WebCore::FontPlatformData:

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Ojan Vafai
On Wed, Jul 22, 2009 at 12:26 PM, Jeremy Orlow wrote: > On Wed, Jul 22, 2009 at 11:57 AM, Ojan Vafai wrote: > >> This is an understatement. We really do a poor job with commit >> descriptions. There is a lot to be gained by having better commit >> descriptions. We can learn from WebKit process h

[chromium-dev] Re: better commit descriptions WAS: Proposal for adding ChangeLog files to Chromium

2009-07-22 Thread Jeremy Orlow
On Wed, Jul 22, 2009 at 11:57 AM, Ojan Vafai wrote: > On Wed, Jul 22, 2009 at 10:07 AM, Darin Fisher wrote: > >> On Wed, Jul 22, 2009 at 10:03 AM, Adam Langley wrote: >> >>> * By having the ChangeLog in the review, reviewers can critique it. >>> >> >>> Many of our commit messages are little bri