From: "Kevin Hilman" <khilman@baylibre.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: kernelci@groups.io, "Rafael J. Wysocki" <rafael@kernel.org>,
info@kernelci.org
Subject: Re: Adding a branch from linux-pm.git to the list of monitored branches
Date: Fri, 20 Dec 2019 14:32:04 -0800 [thread overview]
Message-ID: <m24kxuy6fv.fsf@baylibre.com> (raw)
In-Reply-To: <CAJZ5v0joDseQeuEUXd12ui19MP-v1Szh2G5hjMT1BmjYecEG3g@mail.gmail.com>
"Rafael J. Wysocki" <rafael@kernel.org> writes:
> Hi Kevin,
>
> On Wed, Dec 18, 2019 at 7:58 PM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Hi Rafael,
>>
>> "Rafael J. Wysocki" <rafael@kernel.org> writes:
>>
>> > I think that it would make sense to test at least one branch from the
>> > linux-pm.git tree (for success) before the commits from there go into
>> > linux-next, so I'm wondering if the "testing" branch:
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git testing
>> >
>> > can be added to the list of branches monitored by kernelci?
>>
>> Yes.
>>
>> There are few options when adding a new tree. We have a set of
>> questions in the form of a github issue template. If you don't mind
>> could you select "New kernel branch" from here:
>>
>> https://github.com/kernelci/kernelci-core/issues/new/choose
>>
>> fill out that template answering the few questions.
>
> Well, I needed to create an account on GitHub for that. :-)
If you don't want to do that, you can just copy/paste the text from
this:
https://github.com/kernelci/kernelci-core/blob/master/.github/ISSUE_TEMPLATE/new-kernel-branch.md
into an email, respond to the questions and send here.
Kevin
next prev parent reply other threads:[~2019-12-20 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 10:56 Adding a branch from linux-pm.git to the list of monitored branches Rafael J. Wysocki
2019-12-18 18:58 ` Kevin Hilman
2019-12-19 9:06 ` Rafael J. Wysocki
2019-12-20 22:32 ` Kevin Hilman [this message]
2019-12-22 14:30 ` Rafael J. Wysocki
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=m24kxuy6fv.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=info@kernelci.org \
--cc=kernelci@groups.io \
--cc=rafael@kernel.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.