From: "Moritz Baumann via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Luke Diamand <luke@diamand.org>,
Moritz Baumann <moritz.baumann@sap.com>,
Moritz Baumann <moritz.baumann@sap.com>
Subject: [PATCH v2 1/2] git-p4: fix typo in P4Submit.applyCommit()
Date: Wed, 20 Jul 2022 18:55:29 +0000 [thread overview]
Message-ID: <1484eee8961227a9901e3baa052c74a6d992c220.1658343330.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1297.v2.git.git.1658343330.gitgitgadget@gmail.com>
From: Moritz Baumann <moritz.baumann@sap.com>
Signed-off-by: Moritz Baumann <moritz.baumann@sap.com>
---
git-p4.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-p4.py b/git-p4.py
index 8fbf6eb1fe3..1de3d6f1cd4 100755
--- a/git-p4.py
+++ b/git-p4.py
@@ -2226,7 +2226,7 @@ class P4Submit(Command, P4UserMap):
raw=True):
if regexp.search(line):
if verbose:
- print("got keyword match on %s in %s in %s" % (regex.pattern, line, file))
+ print("got keyword match on %s in %s in %s" % (regexp.pattern, line, file))
kwfiles[file] = regexp
break
--
gitgitgadget
next prev parent reply other threads:[~2022-07-20 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 6:34 [PATCH 0/2] git-p4: fix two undefined variables Moritz Baumann via GitGitGadget
2022-07-20 6:34 ` [PATCH 1/2] git-p4: fix typo in P4Submit.applyCommit() Moritz Baumann via GitGitGadget
2022-07-20 16:09 ` Junio C Hamano
2022-07-20 6:34 ` [PATCH 2/2] git-p4: fix error handling in P4Unshelve.renameBranch() Moritz Baumann via GitGitGadget
2022-07-20 16:18 ` Junio C Hamano
2022-07-20 16:21 ` Junio C Hamano
2022-07-20 17:01 ` Baumann, Moritz
2022-07-20 18:55 ` [PATCH v2 0/2] git-p4: fix two undefined variables Moritz Baumann via GitGitGadget
2022-07-20 18:55 ` Moritz Baumann via GitGitGadget [this message]
2022-07-20 18:55 ` [PATCH v2 2/2] git-p4: fix error handling in P4Unshelve.renameBranch() Moritz Baumann via GitGitGadget
2022-07-20 20:54 ` [PATCH v2 0/2] git-p4: fix two undefined variables Junio C Hamano
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=1484eee8961227a9901e3baa052c74a6d992c220.1658343330.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--cc=moritz.baumann@sap.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.