commit 2f0320c5f24adfee026e938ebc379ca90e3045d3 (patch)
parent e310df70 CLI/git: fix name error
tree fd25feeacea9ee74f4980d29b7cb2cd8bead3dc9
author Jakub Wilk <jwilk@jwilk.net> 2024-01-12 17:27:50 +0100
committer David Bremner <david@tethera.net> 2024-01-14 08:55:20 -0400
CLI/git: remove no-op format() call
---
notmuch-git.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/notmuch-git.py b/notmuch-git.py
index 29f75531..97073c80 100644
--- a/notmuch-git.py
+++ b/notmuch-git.py
@@ -376,7 +376,7 @@ def check_safe_fraction(status):
total = count_messages (TAG_PREFIX)
if total == 0:
- _LOG.error('No existing tags with given prefix, stopping.'.format(safe))
+ _LOG.error('No existing tags with given prefix, stopping.')
_LOG.error('Use --force to override.')
exit(1)
change = len(status['added'])+len(status['deleted'])
glossary
--------
Commit objects reference one tree, and zero or more parents.
Single parent commits can typically generate a patch in
unified diff format via `git format-patch'.
Multiple parents means the commit is a merge.
Root commits have no ancestor. Note that it is
possible to have multiple root commits when merging independent histories.
Every commit references one top-level tree object.
git clone https://yhetil.org/notmuch.git