> On 1 Jun 2020, at 13:33, Graham Leggett <minf...@sharp.fm> wrote: > > On 29 May 2020, at 21:30, Ruediger Pluem <rpl...@apache.org> wrote: > >> changes-fragments/ >> 2.4.41/ >> 2.4.42/ >> 2.4.43/ >> 2.4.44/ And a current/ as symlink? > I’m keen for a simpler version of this that doesn't create additional steps > for people. Not sure that's simpler, though it too has potential. Delete-after-append seems tidier than keeping forever-fragments. I wonder if this could be hooked into SVN? Something like an @CHANGES tag in a svn commit message? -- Nick Kew
- RFC: Documenting changes in the CHANGES file Ruediger Pluem
- Re: RFC: Documenting changes in the CHANGES file Yann Ylavic
- Re: RFC: Documenting changes in the CHANGES file Daniel Ruggeri
- Re: RFC: Documenting changes in the CHANGES fi... Stefan Eissing
- Re: RFC: Documenting changes in the CHANGE... Ruediger Pluem
- Re: RFC: Documenting changes in the CHANGES file Jim Jagielski
- Re: RFC: Documenting changes in the CHANGES file Graham Leggett
- Re: RFC: Documenting changes in the CHANGES file Nick Kew
- Re: RFC: Documenting changes in the CHANGES file Eric Covener