[U-Boot] [ANNOUNCEMENT] Switching to gitlab.denx.de

Patrice CHOTARD patrice.chotard at st.com
Tue Jun 18 07:37:21 UTC 2019

Hi Wolfgang

On 6/17/19 4:42 PM, Wolfgang Denk wrote:
> Hello everybody,
> 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 new URLs for cloning will become
> 	https://gitlab.denx.de/u-boot/u-boot
> for the master repository and
> 	https://gitlab.denx.de/u-boot/custodians/u-boot-XXX
> for the XXX custodian repo.
> Note:
> 	a) These are the Web URLs, from where you also can clone.
> 	   Feel free to add a ".git" to these URLs.
> 	b) SSH access for the custodians is available under
> 	   git at gitlab.denx.de:u-boot/custodians/u-boot-XXX.git
> 	c) git:// access is not available yet; this depends on the
> 	   URL rewrite rules and DNS changes and will be added later
> 	   - ASAP, see below.
> 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.
> 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.
> 6. Everybody is happy.
>    Hopefully.
> OK, at least that's the theory.  If there are problems please let us
> know (me and Harald <hws at denx.de>) and we will do our best to fix
> the issues as fast as possible.
> Thanks, and please keep your finger's crossed.
> Best regards,
> Wolfgang Denk

Patrick Delaunay and i are the STM32 MCU/MPU's U-Boot Maintainers.

Recently Tom let us managed STM32 pull requests from our github temporary waiting for the gitlab migration.

Previously STM-U-boot custodian tree was used but inactive since 2013.

If this repo has been migrated on gitlab, could we get access to it and use it for STM32 ?



More information about the U-Boot mailing list