From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Rebased 4.4 kernel branch
Date: Mon, 22 Oct 2018 09:17:46 +0100 [thread overview]
Message-ID: <1540196266.4503.16.camel@codethink.co.uk> (raw)
Yesterday we discussed how to find the changes in the 4.4-cip branch
relative to 4.4-stable. To this end, I rebased our changes on v4.4.154
(the last version I merged into the -cip branch). I pushed the result
to the linux-4.4.y-cip-rebase branch:
<https://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git/log/?h=linux-4.4.y-cip-rebase>.
The tree is identical to v4.4.154-cip28 but duplicate commits were
dropped and I squashed together all the version updates together.
I don't think this is something that needs to be maintained, but it can
provide a basis for summarising the changes we have currently.
Ben.
--
Ben Hutchings, Software Developer ? Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next reply other threads:[~2018-10-22 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 8:17 Ben Hutchings [this message]
2018-10-25 6:52 ` [cip-dev] Rebased 4.4 kernel branch Nobuhiro Iwamatsu
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=1540196266.4503.16.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox