| 1 |
On Mon, 2 Nov 2015 20:18:07 +0000 |
| 2 |
"Robin H. Johnson" <robbat2@g.o> wrote: |
| 3 |
|
| 4 |
> On Mon, Nov 02, 2015 at 08:05:56AM +0100, Ulrich Mueller wrote: |
| 5 |
> > >>>>> On Mon, 2 Nov 2015, Robin H Johnson wrote: |
| 6 |
> > |
| 7 |
> > > 1. Control of the OUTPUT filename for the generated changelog |
| 8 |
> > > - the from-git generated changelog will go to 'ChangeLog.git' |
| 9 |
> > |
| 10 |
> > > [...] |
| 11 |
> > |
| 12 |
> > > Without #1, we have to rename ALL of the old changelogs, otherwise |
| 13 |
> > > they will be overwritten by the new ones from Git history. |
| 14 |
> > What would be the problem with renaming? IMHO it would be nicer to |
| 15 |
> > keep the ChangeLog name for the autogenerated files and rename the |
| 16 |
> > ones from CVS. We already have files renamed to ChangeLog-<year> |
| 17 |
> > when they became to large, so we could just use ChangeLog-2015 to |
| 18 |
> > stay within that scheme. |
| 19 |
> In the rsync tree, but NOT the Git tree, we have |
| 20 |
> ChangeLog |
| 21 |
> ChangeLog-YYYY |
| 22 |
> Where YYYY so far goes as far as 2014. |
| 23 |
> |
| 24 |
> And 'ChangeLog' files stopped getting updates on August 8th. |
| 25 |
> |
| 26 |
> The old ChangeLog files from CVS are explicitly NOT in Git, but |
| 27 |
> manually injected during the rsync tree creation. |
| 28 |
> |
| 29 |
> If we rename the old ChangeLog files from CVS to ChangeLog-2015, then |
| 30 |
> we'll have both 'ChangeLog-2015' and 'ChangeLog' (generated from Git) |
| 31 |
> containing 2015 entries. Worse, what happens when we hit 2016? Do we |
| 32 |
> merge the old files? |
| 33 |
|
| 34 |
It's not perfectly clean but I don't see any problem here: |
| 35 |
ChangeLog-2015 : all ChangeLog from CVS |
| 36 |
ChangeLog: autogenerated from git |
| 37 |
|
| 38 |
|
| 39 |
if/when there is a need to split git changelogs, autogenerated |
| 40 |
changelogs will start from say, Jan. 1st 2016, and previous changes |
| 41 |
will now be static. Merging CVS2015 and git2015 changelogs is just a |
| 42 |
matter of running a script. Or just skip splitting them for 2016, and |
| 43 |
start splitting in 2017, so that ChangeLog-2015 is CVS ones, |
| 44 |
ChangeLog-2016 is git logs from Aug. 8. 2015 to Dec. 31 2016. |
| 45 |
|
| 46 |
IMHO this is still better than having ChangeLog stopping in 2015 and |
| 47 |
ChangeLog.git starting from this date: Having ChangeLog-2015 from CVS |
| 48 |
still carries partial information on the timeline. |
| 49 |
|
| 50 |
|
| 51 |
Alexis. |
Archives