> On Tue, 29 Nov 2016, Robin H Johnson wrote:
>> - one ChangeLog for each first-level subdir other than categories
>> (i.e. eclass, licenses, profiles, etc.),
> Already done, just querying if profiles/ needs more ChangeLog detail.
Yeah, keep one ChangeLog for all of profiles/. The existing
My question was explicitly asking about profiles/, but I'll respond to
the other pieces in turn.
On Tue, Nov 29, 2016 at 11:59:57PM +0100, Ulrich Mueller wrote:
> I'd say keep it simple:
> - one ChangeLog for each package dir,
Already done.
> - no ChangeLog for category dirs (they contain only a
On Tue, 29 Nov 2016 23:59:57 +0100
Ulrich Mueller wrote:
> > On Tue, 29 Nov 2016, Robin H Johnson wrote:
>
> > TL;DR: Let's replace profiles/**/ChangeLog with profiles/ChangeLog,
> >because it's a mess.
>
> > I'm writing the new changelog generation code [1][2], and I'm
> > wond
> On Tue, 29 Nov 2016, Robin H Johnson wrote:
> TL;DR: Let's replace profiles/**/ChangeLog with profiles/ChangeLog,
>because it's a mess.
> I'm writing the new changelog generation code [1][2], and I'm
> wondering if we can clean up the mess that we have in profiles/.
> The existing
TL;DR: Let's replace profiles/**/ChangeLog with profiles/ChangeLog, because
it's a mess.
I'm writing the new changelog generation code [1][2], and I'm wondering if we
can clean up the mess that we have in profiles/.
The existing Portage egencache --update-changelogs command does NOT gener
