On Mon, Jul 21, 2014 at 11:49:05AM +0400, Yury Gribov wrote: > On 05/09/2014 07:09 PM, Diego Novillo wrote: > > I slightly prefer the semantics that gets me just the ChangeLog. > > The workflow I'm envisioning is: > > I've commited both patches in r212883 and r12884. Mklog now runs as a filter > and prints generated ChangeLog to stdout instead of modifying the patchfile.
thanks for taking care of it! > > OK with Yuri's suggestion of assuming '-' when ARGV is empty. > > I didn't change this because currently empty ARGV is used for printing help > message (similar to some other scripts in contrib/ folder). I'm not really sure which is the better UI, but I'd rather time be spent on better automatic change log generation. I may or may not hope we'll eventually have a mklog that can autogenerate most ChangeLogs and then people will have a hard time arguing they're useful. Trev > > -Y
