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 2/3] branch: fix remotes mapping
Date: Tue, 18 Jun 2019 11:40:24 +0900	[thread overview]
Message-ID: <20190618024025.8274-3-daniel.sangorrin@toshiba.co.jp> (raw)
In-Reply-To: <20190618024025.8274-1-daniel.sangorrin@toshiba.co.jp>

Probably a copy&paste error that never got checked because
nobody is using the mapping functionality.

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
 scripts/kernel_sec/branch.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/kernel_sec/branch.py b/scripts/kernel_sec/branch.py
index 6542415..fb8785c 100644
--- a/scripts/kernel_sec/branch.py
+++ b/scripts/kernel_sec/branch.py
@@ -214,7 +214,7 @@ def get_remotes(mappings, mainline=None, stable=None):
         _get_configured_remotes(
             os.path.expanduser('~/.config/kernel-sec/remotes.yml')))
     for mapping in mappings:
-        left, right = arg.split(':', 1)
+        left, right = mapping.split(':', 1)
         remotes[left]['git_name'] = right
     if mainline:
         remotes['torvalds']['git_name'] = mainline
-- 
2.17.1

  parent reply	other threads:[~2019-06-18  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  2:40 [cip-dev] patches to check remotes Daniel Sangorrin
2019-06-18  2:40 ` [cip-dev] [cip-kernel-sec 1/3] remotes: check that remotes exist Daniel Sangorrin
2019-06-18 15:07   ` Ben Hutchings
2019-06-20  5:54     ` daniel.sangorrin at toshiba.co.jp
2019-06-18  2:40 ` Daniel Sangorrin [this message]
2019-06-18 15:08   ` [cip-dev] [cip-kernel-sec 2/3] branch: fix remotes mapping Ben Hutchings
2019-06-18  2:40 ` [cip-dev] [cip-kernel-sec 3/3] help:remote_name: use colon instead of equal Daniel Sangorrin
2019-06-18 15:08   ` 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=20190618024025.8274-3-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.