All of
 help / color / mirror / Atom feed
From: (Ben Hutchings)
Subject: [cip-dev] [cip-kernel-sec 1/2] remotes: automatically add remotes from configuration file
Date: Tue, 18 Jun 2019 14:00:47 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 2019-06-18 at 03:54 +0000, daniel.sangorrin at wrote:
> > > > From: Ben Hutchings <>
> > On Mon, 2019-06-17 at 14:21 +0900, Daniel Sangorrin wrote:
> > > Currently the user is required to create its own remotes by
> > > hand. This should not be necessary, because the information
> > > is already collected in conf/remotes.yml. For that reason,
> > > if we detect that any remote has not been added to the
> > > local repo then we will add those.
> > 
> > I'm not yet convinced this is a good idea.
> I sent a new patch that takes a different approach. The new patch will
> only check that the necessary remotes are there. I also prepared a
> new separate script, for new users to prepare the local repository.
> > After this change, we would still be assuming that there is a kernel
> > repository or working tree next to kernel-config.??If we wanted to be
> > really helpful we could create a new repository if it's not there.
> I didn't understand the kernel-config thing. Maybe I am missing something important.

Sorry, I meant "next to kernel-sec".


Ben Hutchings, Software Developer                ?        Codethink Ltd                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom

      reply	other threads:[~2019-06-18 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17  5:21 Daniel Sangorrin
2019-06-17  5:21 ` [cip-dev] [cip-kernel-sec 2/2] git_repo: add a check for the git_repo directory Daniel Sangorrin
2019-06-17 20:54 ` [cip-dev] [cip-kernel-sec 1/2] remotes: automatically add remotes from configuration file Ben Hutchings
2019-06-18  3:54   ` daniel.sangorrin at
2019-06-18 13:00     ` 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:

* 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: automatically add remotes from configuration file' \

* 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.