From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] [vcstocl] Import ProjectQuirks from its own file
Date: Thu, 20 Aug 2020 08:52:19 +0530 [thread overview]
Message-ID: <20200820032219.798899-1-siddhesh@sourceware.org> (raw)
In-Reply-To: <a5441545-82b6-7fbe-8d7f-040e094038db@cs.ucla.edu>
ProjectQuirks moved into its own file in gnulib because one cannot
import modules with hyphens in them. Adjust the quirks file to
reflect this reality.
[1] https://lists.gnu.org/archive/html/bug-gnulib/2020-08/msg00177.html
[2] https://lists.gnu.org/archive/html/bug-gnulib/2020-08/msg00178.html
---
Sorry, I missed the quirks file dependency when I renamed
vcs-to-changelog in gnulib. I have posted patches[1][2] to split the
ProjectQuirks class out into its own file since that is a cleaner
solution. I'll commit this once the changes to gnulib are accepted.
scripts/vcstocl_quirks.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/vcstocl_quirks.py b/scripts/vcstocl_quirks.py
index d73a586317..b79b5d954e 100644
--- a/scripts/vcstocl_quirks.py
+++ b/scripts/vcstocl_quirks.py
@@ -17,7 +17,7 @@
# <http://www.gnu.org/licenses/>.
from frontend_c import Frontend
-from vcs_to_changelog import ProjectQuirks
+from projectquirks import ProjectQuirks
import re
class GlibcProjectQuirks(ProjectQuirks):
--
2.26.2
prev parent reply other threads:[~2020-08-20 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 20:34 Autogenerating ChangeLog for glibc did not work as intended Carlos O'Donell
2020-08-19 22:14 ` Paul Eggert
2020-08-20 3:22 ` Siddhesh Poyarekar [this message]
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=20200820032219.798899-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.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).