This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Git ChangeLog policy for GCC Testsuite inquiry
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Eric Botcazou <ebotcazou at adacore dot com>, gcc at gcc dot gnu dot org, David Edelsohn <dje dot gcc at gmail dot com>, Jason Merrill <jason at redhat dot com>
- Date: Fri, 24 Jan 2020 22:45:33 +0100
- Subject: Re: Git ChangeLog policy for GCC Testsuite inquiry
- References: <CAGWvnyktjKVp-T9jrGUt_rmzgaoS0Z5N1OPP9oaOvk0Xehrb_Q@mail.gmail.com> <CAGWvnym24or6ix3-vOkF=3oZ46LCnStm58+QQzVL62gjboN+Jw@mail.gmail.com> <0829cb62791e9d8d034309f09b6c911ed8340c8b.camel@redhat.com> <1693150.uSzEE5ffML@polaris> <df5a09ce54d07c7bb60b4e00b76e7b4673779333.camel@redhat.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Jan 24, 2020 at 02:36:31PM -0700, Jeff Law wrote:
> On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote:
> > > I strongly prefer to move towards relying on the git log.
> >
> > In my experience the output of git log is a total mess so cannot replace
> > ChangeLogs. But we can well decide to drop ChangeLog for the testsuite.
> Well, glibc has moved to extracting them from git, building policies
> and scripts around that. I'm pretty sure other significant projecs are
> also extracting their ChangeLogs from git.
>
> We could do the same, selecting some magic date as the cutover point
> after which future ChangeLogs are extracted from GIT. In fact, that's
> precisely what I'd like to see us do.
We don't have a tool that can do it, not even get the boilerplate right.
Yes, mklog helps, but it very often gets stuff wrong. Not to mention that
the text what actually changed can't be generated very easily.
Jakub