This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2/2] allow running mklog as a filter

On Mon, Jul 28, 2014 at 10:42:51AM +0400, Yury Gribov wrote:
> On 07/21/2014 12:55 PM, Trevor Saunders wrote:
> >I'm not really sure which is the better UI,
> >but I'd rather time be spent
> >on better automatic change log generation.
> Yeah. Do you have some particular complaints btw?

I haven't actually used it in a while, but istr there's an issue where
if you change the prototype of a function mklog makes an entry for the
previous function.

Automatically inserting likewise where it would be appropriate would be
nice, but fairly hard I suspect.

> >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.
> I wonder how many GCC developers actually use the script (our team does).

Not sure.  I actually haven't used it ina while because I've mostly been
generating patches where it was easier to do one entry for a ton of
files so it was easier to generate that with git diff and sed.


> -Y

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]