From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-kernel-sec 2/2] remotes: call _get_configured_remotes
Date: Mon, 17 Jun 2019 11:20:39 +0900 [thread overview]
Message-ID: <20190617022039.7197-2-daniel.sangorrin@toshiba.co.jp> (raw)
In-Reply-To: <20190617022039.7197-1-daniel.sangorrin@toshiba.co.jp>
This is probably a copy&paste mistake that had no effect
because the contents of _get_configured_remotes and
_get_configured_branches is the same.
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 ae1ca2c..3ede64a 100644
--- a/scripts/kernel_sec/branch.py
+++ b/scripts/kernel_sec/branch.py
@@ -209,7 +209,7 @@ def get_remotes(mappings, mainline=None, stable=None):
remotes = RemoteMap()
remotes.update(_get_configured_remotes('conf/remotes.yml'))
remotes.update(
- _get_configured_branches(
+ _get_configured_remotes(
os.path.expanduser('~/.config/kernel-sec/remotes.yml')))
for mapping in mappings:
left, right = arg.split(':', 1)
--
2.17.1
next prev parent reply other threads:[~2019-06-17 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 2:20 [cip-dev] [cip-kernel-sec 1/2] remotes: refer to configuration files Daniel Sangorrin
2019-06-17 2:20 ` Daniel Sangorrin [this message]
2019-06-17 20:16 ` [cip-dev] [cip-kernel-sec 2/2] remotes: call _get_configured_remotes Ben Hutchings
2019-06-17 23:48 ` daniel.sangorrin at toshiba.co.jp
2019-06-18 14:42 ` Ben Hutchings
2019-06-17 20:15 ` [cip-dev] [cip-kernel-sec 1/2] remotes: refer to configuration files 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=20190617022039.7197-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.