From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANNOUNCEMENT] Switching to gitlab.denx.de
Date: Tue, 18 Jun 2019 15:46:56 +0200 [thread overview]
Message-ID: <20190618134656.96B43241D29@gemini.denx.de> (raw)
Hello everybody,
I wrote:
> as discussed before, we want to switch from the old git server to
> more powerful soft- and hardware. We will move the U-Boot master
> repository and all custodian repositories to gitlab.
...
> The switch will take place as follows:
>
> 1. We will create user accounts for all custodians at gitlab.denx.de
> You will receive an e-mail notification with your login
> credentials. We will start with this this afternoon (CEST),
> so if you have not received such an e-mail by tomorrow morning,
> please let us know.
>
> 2. We will block your SSH keys on the old git server, thus
> effectively turning the custodian repositories into read-only
> mode. Custodians will not be able to push any new stuff to the
> old repositories any more.
>
> This phase will start when all custodian repositories have been
> created, but in no case before 12:00 p. m. (noon) CEST. the
> next steps will follow as quickly as possible, ideally only a few
> minutes later.
>
> 3. The old repository will be cloned to the new gitlab server. This
> should not take long. We don't expect any long interruption.
> You wanted to have another cup of coffee anyway :-)
>
> 4. The custodian can resume work using the gitlab server, as soon as
> he can "see" his repository there. Tom should already be
> prepared to pull from the gitlab repos.
All these steps have been completed by now. All custodians should
be able to access the new repositories now, and use all teh gitlab
features that are enabled for this project (including CI runners).
The U-Boot web pages (especially the source code links and the
custodian page) have been updated to reference the new gitlab
repositories.
By now, the gitlab repos represent the official and active mainline
/ custodian repositories.
> 5. After all custodians have been moved, URL rewrite rules will be
> activated, and the DNS will be changed, so that the old URLs
> will still be working, though only for read-only access.
>
> Note: this last step is the most error-prone one. It is likely
> that the rewrite roles are incomplete at the beginning, and/or
> incorrect for a few special cases. Please be patient and report
> such errors with enough detail to reproduce, then we will fix
> them.
This is what we will be working on now.
Thanks for your patience!
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Living on Earth may be expensive, but it includes an annual free trip
around the Sun.
next reply other threads:[~2019-06-18 13:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 13:46 Wolfgang Denk [this message]
2019-06-18 14:04 ` [U-Boot] [U-Boot-Custodians] [ANNOUNCEMENT] Switching to gitlab.denx.de Daniel Schwierzeck
2019-06-18 14:50 ` Wolfgang Denk
2019-06-18 15:55 ` Bin Meng
2019-06-19 11:47 ` Patrice CHOTARD
2019-06-18 20:08 ` Joe Hershberger
2019-06-18 20:49 ` Heinrich Schuchardt
2019-06-18 21:08 ` Anatolij Gustschin
2019-06-19 13:33 ` Harald Seiler
2019-06-19 18:29 ` Joe Hershberger
2019-06-19 13:29 ` Harald Seiler
2019-06-19 4:59 ` [U-Boot] " Mario Six
2019-06-19 22:38 ` [U-Boot] [U-Boot-Custodians] " Angelo Dureghello
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FA40D8943@ATCPCS16.andestech.com>
2019-07-01 9:53 ` [U-Boot] " Rick Chen
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 14:42 Wolfgang Denk
2019-06-18 7:37 ` Patrice CHOTARD
2019-06-18 7:46 ` Wolfgang Denk
2019-06-18 8:49 ` Patrice CHOTARD
2019-06-18 12:00 ` Tom Rini
2019-06-18 16:58 ` Tom Rini
2019-06-19 13:14 ` Harald Seiler
2019-06-19 13:19 ` Tom Rini
2019-06-20 6:42 ` Peng Fan
2019-06-24 13:04 ` Harald Seiler
2019-06-24 15:21 ` Tom Rini
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=20190618134656.96B43241D29@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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