From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: bug-gnulib@gnu.org
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>
Subject: [PATCH 2/3] vcs-to-changelog: Fix formatting of ChangeLog ouput
Date: Thu, 16 Jan 2020 12:49:54 +0530 [thread overview]
Message-ID: <20200116071955.61450-3-siddhesh@gotplt.org> (raw)
In-Reply-To: <20200116071955.61450-1-siddhesh@gotplt.org>
Add another newline when the number of files differing is too large.
This is typical for across-the-board changes such as copyright year
updates.
* build-aux/vcstocl/vcs_git.py (list_changes): Add newline in
print output.
---
build-aux/vcstocl/vcs_git.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/build-aux/vcstocl/vcs_git.py b/build-aux/vcstocl/vcs_git.py
index 0b8099e0b..23ede3b5a 100644
--- a/build-aux/vcstocl/vcs_git.py
+++ b/build-aux/vcstocl/vcs_git.py
@@ -101,7 +101,7 @@ class GitRepo:
# updates, copyright notice changes, etc.) and likely not interesting
# enough to produce a detailed ChangeLog entry.
if len(op) > 100:
- print('\t* Suppressing diff as too many files differ.')
+ print('\t* Suppressing diff as too many files differ.\n')
return
# Each of these lines has a space separated format like so:
--
2.24.1
next prev parent reply other threads:[~2020-01-16 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 7:19 [PATCH 0/3] vcs-to-changelog fixes Siddhesh Poyarekar
2020-01-16 7:19 ` [PATCH 1/3] vcs-to-changelog: Drop python3 shebang from frontend_c.py Siddhesh Poyarekar
2020-01-16 7:19 ` Siddhesh Poyarekar [this message]
2020-01-16 7:19 ` [PATCH 3/3] vcs-to-changelog: Allow loading of custom quirks file Siddhesh Poyarekar
2020-01-16 20:32 ` [PATCH 0/3] vcs-to-changelog fixes Bruno Haible
2020-01-17 3:39 ` 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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200116071955.61450-3-siddhesh@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=bug-gnulib@gnu.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).