All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-kernel-sec][PATCH v2 2/3] help:remote_name: use colon instead of equal
Date: Thu, 20 Jun 2019 14:51:42 +0900	[thread overview]
Message-ID: <20190620055143.341-2-daniel.sangorrin@toshiba.co.jp> (raw)
In-Reply-To: <20190620055143.341-1-daniel.sangorrin@toshiba.co.jp>

The example and implementation use a colon (:) to specify
remote mappings, but the command's help use the equal
sign (=).

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
 scripts/import_stable.py   | 2 +-
 scripts/report_affected.py | 2 +-
 scripts/webview.py         | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/scripts/import_stable.py b/scripts/import_stable.py
index b3261cf..2c88b07 100755
--- a/scripts/import_stable.py
+++ b/scripts/import_stable.py
@@ -174,7 +174,7 @@ if __name__ == '__main__':
     parser.add_argument('--remote-name',
                         dest='remote_name', action='append', default=[],
                         help='git remote name mappings, e.g. stable:korg-stable',
-                        metavar='NAME=OTHER-NAME')
+                        metavar='NAME:OTHER-NAME')
     parser.add_argument('--mainline-remote',
                         dest='mainline_remote_name',
                         help="git remote name to use instead of 'torvalds'",
diff --git a/scripts/report_affected.py b/scripts/report_affected.py
index fac0885..879c021 100755
--- a/scripts/report_affected.py
+++ b/scripts/report_affected.py
@@ -76,7 +76,7 @@ if __name__ == '__main__':
     parser.add_argument('--remote-name',
                         dest='remote_name', action='append', default=[],
                         help='git remote name mappings, e.g. stable:korg-stable',
-                        metavar='NAME=OTHER-NAME')
+                        metavar='NAME:OTHER-NAME')
     parser.add_argument('--mainline-remote',
                         dest='mainline_remote_name',
                         help="git remote name to use instead of 'torvalds'",
diff --git a/scripts/webview.py b/scripts/webview.py
index 9e16a0c..a3a643b 100755
--- a/scripts/webview.py
+++ b/scripts/webview.py
@@ -206,7 +206,7 @@ if __name__ == '__main__':
     parser.add_argument('--remote-name',
                         dest='remote_name', action='append', default=[],
                         help='git remote name mappings, e.g. stable:korg-stable',
-                        metavar='NAME=OTHER-NAME')
+                        metavar='NAME:OTHER-NAME')
     parser.add_argument('--mainline-remote',
                         dest='mainline_remote_name',
                         help="git remote name to use instead of 'torvalds'",
-- 
2.17.1

  reply	other threads:[~2019-06-20  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  5:51 [cip-dev] [cip-kernel-sec][PATCH v2 1/3] branch: fix remotes mapping Daniel Sangorrin
2019-06-20  5:51 ` Daniel Sangorrin [this message]
2019-06-20  5:51 ` [cip-dev] [cip-kernel-sec][PATCH v2 3/3] remotes: check that remotes exist Daniel Sangorrin
2019-06-20 18:07   ` Ben Hutchings
2019-06-20 18:08 ` [cip-dev] [cip-kernel-sec][PATCH v2 1/3] branch: fix remotes mapping Ben Hutchings

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=20190620055143.341-2-daniel.sangorrin@toshiba.co.jp \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.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 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.