This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>
- Cc: Florian Weimer <fweimer at redhat dot com>, "Gabriel F. T. Gomes" <gabriel at inconstante dot net dot br>, <libc-alpha at sourceware dot org>
- Date: Fri, 11 Oct 2019 20:27:16 +0000
- Subject: Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- Ironport-sdr: EfJwc8wawRkrbW8AlKJSbWEKdlE70fo5PMBkkTsVWEls+sE7IExvT3uXbAMuf1p+0mo7e1/ZH/ 9RJiR+QB/GoG9avhdpQC58hkN9Y5ui8gyXzgOXgblLCvAaWMlEDEY8AYp0cwezCa+UPp2hWR5U fii69s39nanKIC3PQlsC6qeiba/pilsQ8GkYQuoivg70V/78/mpQokGGFF9hFyTCIvsWUQBmJr O2sXsiVur1JNBY/PlPnzM2zP0aIv3GJe7t5jB5O7lMD9T2lNw9dWiDpdAKzr8PMLlUlgNOnnyN GW0=
- Ironport-sdr: 0OQV1iMTLt9QC0ngyyitX7Py5tVLQn0pbry5vx8gb6ob7Cez8NKrv7O4A/AapRSYe+/KnnR41A ArE/l2KyL3sESmjABnS+x7piqQFdDGaORnXWWphXUWChRC17gJJTqhBKJFxh3dMQd2rv5JnWTK uMxS1ngMdozXDV8b/C0cxOHREWaFK7tkyrEy8z0JQzoGyrthldr9rZ/uZa/VtoDyxxVetos4MK 52xoHPX5juzaQTK3zMDKXcSPdmjkUcdA2TZzy6NfiJBmy80XExbEoUogudpMhrLdSda8J9D01+ ujc=
- References: <87wode75tm.fsf@oldenburg2.str.redhat.com> <20191009102348.16dd1125@tereshkova> <alpine.DEB.2.21.1910091616280.19032@digraph.polyomino.org.uk> <87wodbgidw.fsf@oldenburg2.str.redhat.com> <alpine.DEB.2.21.1910112020200.2657@digraph.polyomino.org.uk> <7a7e0d9d-1b02-8e4b-63c6-5ba24ed7726c@gotplt.org>
On Fri, 11 Oct 2019, Siddhesh Poyarekar wrote:
> On 11/10/19 4:21 pm, Joseph Myers wrote:
> > I support renaming it now, and making the wiki documentation of the
> > release process name the relevant commit as the starting point for
> > ChangeLog generation for the 2.31 release.
> >
>
> This is a pretty significant change in our processes, so just adding a
> tag (changelogs-end-here or similar) may not be a bad idea IMO. It
> doesn't have to be a signed tag since it is not really release-critical.
If we add a tag, it specifically should *not* be an annotated tag because
that would affect "git describe" output.
--
Joseph S. Myers
joseph@codesourcery.com