From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, tkjos@google.com, kernelci@groups.io
Cc: Matt Hart <matthew.hart@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>
Subject: Re: Please add/remove android branches from kernelci + clang builds
Date: Wed, 21 Aug 2019 13:21:01 -0700 [thread overview]
Message-ID: <7hsgpu9snm.fsf@baylibre.com> (raw)
In-Reply-To: <CAHRSSExgOW4CWc_YfUQcx_sJYanBNTrLiNntt67zxcWUPudcjQ@mail.gmail.com>
" via Groups.Io" <tkjos=google.com@groups.io> writes:
> 4 requests related to android kernels (repo:
> https://android.googlesource.com/kernel/common):
>
> 1) android-4.14 is being moved to android-4.14-r (currently mirrored
> so testing can be moved to new branch)
>
> delete: android-4.14
> add: android-4.14-r
>
> 2) android-4.19 is being moved to android-4.19-r (currently mirrored
> so testing can be moved to new branch)
>
> delete: android-4.19
> add: android-4.19-r
>
> 3) android-4.9 is obsolete
>
> delete: android-4.19
I assume you meant android-4.9 here (based on the previous sentence)?
Kevin
next prev parent reply other threads:[~2019-08-21 20:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 18:25 Please add 3 android common kernels to kernelci Todd Kjos
2019-05-15 12:03 ` Matt Hart
2019-05-16 11:48 ` Matt Hart
2019-05-16 16:19 ` Todd Kjos
2019-07-02 19:16 ` Please remove android-4.4 from kernelci Todd Kjos
2019-07-03 14:43 ` Matt Hart
2019-08-21 18:03 ` Please add/remove android branches from kernelci + clang builds Todd Kjos
2019-08-21 20:21 ` Kevin Hilman [this message]
2019-08-21 20:26 ` Todd Kjos
2019-08-22 16:53 ` Matt Hart
2019-08-22 16:55 ` Todd Kjos
2019-08-22 17:08 ` Matt Hart
2019-08-22 17:14 ` Todd Kjos
2019-11-15 1:25 ` Todd Kjos
2019-11-21 21:54 ` Todd Kjos
2019-11-21 23:40 ` Kevin Hilman
2019-11-22 0:17 ` Todd Kjos
2019-11-21 23:39 ` Kevin Hilman
2019-11-22 0:18 ` Todd Kjos
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=7hsgpu9snm.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=anmar.oueja@linaro.org \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
--cc=tkjos@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox