From: Paul Eggert <eggert@cs.ucla.edu>
To: Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>,
Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: Re: Autogenerating ChangeLog for glibc did not work as intended.
Date: Wed, 19 Aug 2020 15:14:53 -0700 [thread overview]
Message-ID: <a5441545-82b6-7fbe-8d7f-040e094038db@cs.ucla.edu> (raw)
In-Reply-To: <9c78230b-c9e7-f0b6-078c-3b3d55943dff@redhat.com>
On 8/19/20 1:34 PM, Carlos O'Donell wrote:
> What should we be doing in glibc's scripts/vcstocl_quirks.py to make this work?
Most likely just remove its "from vcs_to_changelog import ProjectQuirks" line.
But I haven't tested this, and Siddhesh is the real expert here.
next prev parent reply other threads:[~2020-08-19 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 20:34 Carlos O'Donell
2020-08-19 22:14 ` Paul Eggert [this message]
2020-08-20 3:22 ` [PATCH] [vcstocl] Import ProjectQuirks from its own file Siddhesh Poyarekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5441545-82b6-7fbe-8d7f-040e094038db@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).