This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [2.30][RFC] vcs-to-changelog quirks file for glibc
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Siddhesh Poyarekar <siddhesh at sourceware dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, "Carlos O'Donell" <carlos at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Sun, 27 Jan 2019 08:54:31 -0800
- Subject: Re: [2.30][RFC] vcs-to-changelog quirks file for glibc
- References: <20190127162522.5671-1-siddhesh@sourceware.org>
On Sun, Jan 27, 2019 at 8:26 AM Siddhesh Poyarekar
<siddhesh@sourceware.org> wrote:
>
> A vcs-to-changelog script set has been posted on the gnulib mailing
> list (archive not updated yet) and this script uses a quirks file in
> the project for a number of things including determining the target
> VCS and macro substitutions that are needed to allow the frontend
> parser in the script to work correctly.
>
> This is the glibc quirks file that makes a number of substitutions
> including all the libc-symbol hack macros.
>
> ---
>
> If all goes well, I intend to add this quirks file immediately upon
> opening 2.30 development on master so that we don't have to put in
> ChangeLog entries from 2.30 onwards. Does that sound acceptable? This
> is of course assuming that the script is at least accepted in principle
> in gnulib, i.e. the approach is considered acceptable and we only need
> to iterate on making sure that code quality standards are met.
>
> Siddhesh
>
> vcstocl_quirks.py | 64 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 64 insertions(+)
> create mode 100644 vcstocl_quirks.py
>
> diff --git a/vcstocl_quirks.py b/vcstocl_quirks.py
> new file mode 100644
> index 0000000000..b29ea56031
> --- /dev/null
> +++ b/vcstocl_quirks.py
Should it be in the "script" directory?
--
H.J.