From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-kernel-sec][PATCH v2 1/3] branch: fix remotes mapping
Date: Thu, 20 Jun 2019 19:08:05 +0100 [thread overview]
Message-ID: <1561054085.21054.49.camel@codethink.co.uk> (raw)
In-Reply-To: <20190620055143.341-1-daniel.sangorrin@toshiba.co.jp>
I've applied this and the following patch, as they're obviously
correct.
Ben.
On Thu, 2019-06-20 at 14:51 +0900, Daniel Sangorrin wrote:
> 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 3ede64a..10f3339 100644
> --- a/scripts/kernel_sec/branch.py
> +++ b/scripts/kernel_sec/branch.py
> @@ -212,7 +212,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
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-06-20 18:08 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 ` [cip-dev] [cip-kernel-sec][PATCH v2 2/3] help:remote_name: use colon instead of equal Daniel Sangorrin
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 ` Ben Hutchings [this message]
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=1561054085.21054.49.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--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.