All of
 help / color / mirror / Atom feed
From: (Daniel Sangorrin)
Subject: [cip-dev] [cip-kernel-sec 1/2] remotes: refer to configuration files
Date: Mon, 17 Jun 2019 11:20:38 +0900	[thread overview]
Message-ID: <> (raw)

The Readme indicated some remote names (torvalds, stable) but
not all of them. Ask the user to check conf/remotes.yml instead.
I also added information on how to override or extend the
configuration file (through '~/.config/kernel-sec/remotes.yml')

Signed-off-by: Daniel Sangorrin <>
--- | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/ b/
index a4f3d45..4c5808f 100644
--- a/
+++ b/
@@ -18,9 +18,10 @@ beneath that.  They require PyYAML and html5lib (packaged in Debian as
 python3-yaml and python3-html5lib).
 Many scripts require access to a kernel git repository.  By default
-this is assumed to be in `../kernel`, with remotes named `torvalds`
-and `stable` for the mainline and stable repositories.  These can
-be overridden by command-line options or by configuration.
+this is assumed to be in `../kernel`, with remotes configured in
+`conf/remotes.yml`, e.g. `torvalds`, `stable` and `cip` for the mainline,
+stable and cip repositories. These can be overridden by command-line options
+or configuration (`~/.config/kernel-sec/remotes.yml`).
 * `scripts/` - import information from Debian's
 `kernel_sec` project.  It includes all issues that Debian considers

             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 Daniel Sangorrin [this message]
2019-06-17  2:20 ` [cip-dev] [cip-kernel-sec 2/2] remotes: call _get_configured_remotes Daniel Sangorrin
2019-06-17 20:16   ` Ben Hutchings
2019-06-17 23:48     ` daniel.sangorrin at
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: [cip-dev] [cip-kernel-sec 1/2] remotes: refer to configuration files' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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.