On Mon, Nov 02, 2015 at 08:05:56AM +0100, Ulrich Mueller wrote: > >>>>> On Mon, 2 Nov 2015, Robin H Johnson wrote: > > > 1. Control of the OUTPUT filename for the generated changelog > > - the from-git generated changelog will go to 'ChangeLog.git' > > > [...] > > > Without #1, we have to rename ALL of the old changelogs, otherwise > > they will be overwritten by the new ones from Git history. > What would be the problem with renaming? IMHO it would be nicer to > keep the ChangeLog name for the autogenerated files and rename the > ones from CVS. We already have files renamed to ChangeLog-<year> when > they became to large, so we could just use ChangeLog-2015 to stay > within that scheme. In the rsync tree, but NOT the Git tree, we have ChangeLog ChangeLog-YYYY Where YYYY so far goes as far as 2014.
And 'ChangeLog' files stopped getting updates on August 8th. The old ChangeLog files from CVS are explicitly NOT in Git, but manually injected during the rsync tree creation. If we rename the old ChangeLog files from CVS to ChangeLog-2015, then we'll have both 'ChangeLog-2015' and 'ChangeLog' (generated from Git) containing 2015 entries. Worse, what happens when we hit 2016? Do we merge the old files? The main tree Git history starts at August 8th, so it can't be used to generate older entries either (ignoring using the full history to generate full ChangeLog.git files since the start of time, because CVS commit messages used to be a LOT worse than the manual ChangeLog messages). Thus, I was proposing to explicitly name the from-git ChangeLog as ChangeLog.git or ChangeLog-git. -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
