From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP kernel in Gitlab.com
Date: Mon, 6 Mar 2017 16:19:45 +0100 [thread overview]
Message-ID: <58BD7E11.2080200@codethink.co.uk> (raw)
Hi,
the past few weeks, maybe related with the problems gitlab.com has
experienced, the automatic update of our kernel in gitlab.com has given
us problems to the extend that we took two actions:
* Disable the automatic updates
* Use directly the kernel.org repo in Board at desk - single dev
Since the week before I was at ELC and last week on vacation, the CIP
kernel is not up to date compared to the kernel.org one. I am currently
updating it.
I am monitoring gitlab.com service. I hope I can restore the automatic
updates soon. Meanwhile, I will update it manually at least on weekly basis.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
reply other threads:[~2017-03-06 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=58BD7E11.2080200@codethink.co.uk \
--to=agustin.benito@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