-100 million to changelogs.

On Wed, Jul 22, 2009 at 8:28 AM, Anthony LaForge<lafo...@google.com> wrote:
> It also strikes me that we'd have have trouble filtering out reverts using
> the RELEASE_NOTE tag.  Since the original change with the RELEASE_NOTE tag
> and the reverted change would be in different revisions I'm not sure a
> simple grep would suffice.
> Kind Regards,
>
> Anthony Laforge
> Technical Program Manager
> Mountain View, CA
>
>
> On Tue, Jul 21, 2009 at 11:08 PM, Anthony LaForge <lafo...@google.com>
> wrote:
>>
>> The main advantage that I could see for a file would be that I could point
>> people to a single file (at any given revision) which could tell then the
>> exact state of feature work and history.  It seems to me that the
>> RELEASE_NOTE tag would be more cumbersome.
>> Kind Regards,
>>
>> Anthony Laforge
>> Technical Program Manager
>> Mountain View, CA
>>
>>
>> On Tue, Jul 21, 2009 at 10:27 PM, Evan Martin <e...@chromium.org> wrote:
>>>
>>> On Tue, Jul 21, 2009 at 10:22 PM, Adam Langley<a...@chromium.org> wrote:
>>> >
>>> > On Tue, Jul 21, 2009 at 9:37 PM, Anthony LaForge<lafo...@google.com>
>>> > wrote:
>>> >> In order to make it easier for the community to see the changes are
>>> >> going on
>>> >> inside Chromium I'd like to propose that we add one or more ChangeLog
>>> >> files
>>> >> into our code base.  The proposed usage would go something like this:
>>> >
>>> > I'm not saying anything that Jeremy and Adam haven't already said,
>>> > just reinforcing their point in case there's any question.
>>> >
>>> > What you want is `git log | grep RELEASE_NOTE`
>>>
>>> git log --grep=RELEASE_NOTE
>>> will show the full log entries that match that text.
>>>
>>> PS: I've gotta be 100% on responding to threads that mention git, huh.
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to