[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21998: Run 'make change-history' on release branch
From: |
Eli Zaretskii |
Subject: |
bug#21998: Run 'make change-history' on release branch |
Date: |
Mon, 07 Mar 2016 19:00:37 +0200 |
> From: John Wiegley <jwiegley@gmail.com>
> Cc: rms@gnu.org, 21998@debbugs.gnu.org
> Date: Mon, 07 Mar 2016 08:35:16 -0800
>
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
> > . Keep the current system, where ChangeLog is produced from Git log
> > and mistakes made in Git log should be corrected manually after
> > producing ChangeLog
>
> If you really do want to keep ChangeLogs around, I'd prefer this over the
> third option.
That's the system we tried for the past year, and it clearly failed.
Why should we continue to invest good money after bad money?
Is it really that hard to copy/paste an entry from the ChangeLog to
Git log, or the other way around?
bug#21998: Run 'make change-history' on release branch, Glenn Morris, 2016/03/08
bug#21998: Run 'make change-history' on release branch, Richard Stallman, 2016/03/07
bug#21998: Run 'make change-history' on release branch, Richard Stallman, 2016/03/08
bug#21998: Run 'make change-history' on release branch, Eli Zaretskii, 2016/03/08
bug#21998: Run 'make change-history' on release branch, Richard Stallman, 2016/03/09
bug#21998: Run 'make change-history' on release branch, Eli Zaretskii, 2016/03/09
bug#21998: Run 'make change-history' on release branch, Richard Stallman, 2016/03/10
bug#21998: Run 'make change-history' on release branch, Eli Zaretskii, 2016/03/11
bug#21998: Run 'make change-history' on release branch, Nicolas Petton, 2016/03/11