Bug 135542

Summary: prepare-ChangeLog --no-write shouldn’t require ChangeLog to exist
Product: WebKit Reporter: mitz
Component: Tools / TestsAssignee: mitz
Status: RESOLVED FIXED    
Severity: Normal CC: thorton
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Do not require ChangeLog to exist when --no-write is specified thorton: review+

mitz
Reported 2014-08-02 10:06:43 PDT
Since it’s not writing the any ChangeLog files, prepare-ChangeLog --no-write should not require a ChangeLog file to exist at or above the directory each changed file is in. It can just output the entry for the top level anyway.
Attachments
Do not require ChangeLog to exist when --no-write is specified (2.28 KB, patch)
2014-08-02 10:08 PDT, mitz
thorton: review+
mitz
Comment 1 2014-08-02 10:08:57 PDT
Created attachment 235936 [details] Do not require ChangeLog to exist when --no-write is specified
mitz
Comment 2 2014-08-02 10:35:02 PDT
Note You need to log in before you can comment on or make changes to this bug.