public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Eugen.Hristev@microchip.com
Cc: u-boot@lists.denx.de
Subject: Re: Rename of the u-boot-atmel custodian tree
Date: Thu, 26 Aug 2021 08:44:01 -0400	[thread overview]
Message-ID: <20210826124401.GH858@bill-the-cat> (raw)
In-Reply-To: <c5ae40ab-e6b0-cf14-5912-4044d5160a6a@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Thu, Aug 26, 2021 at 07:17:24AM +0000, Eugen.Hristev@microchip.com wrote:

> Hello everyone,
> 
> I plan to rename the u-boot-atmel tree to u-boot-at91 .
> 
> It's been more than 5 years since Atmel is part of Microchip, and the 
> name is slowly being changed to reflect the new reality.
> 
> It makes more sense to have the custodian tree named u-boot-at91 , as 
> this tree is used only for patches related to the at91 boards and 
> drivers (not any other former Atmel product, nor any other Microchip 
> product ). I won't be naming it u-boot-microchip since Microchip does 
> much more than just the former Atmel MPUs (AT91 architecture) .
> 
> This means, however, that all remotes to this tree have to be updated.
> I do not see any other side effect at this moment.
> 
> I will wait some more time , few weeks or one month, before making this 
> change, to allow anyone to comment on this.

Sounds like a good plan to me, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2021-08-26 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26  7:17 Rename of the u-boot-atmel custodian tree Eugen.Hristev
2021-08-26 12:44 ` Tom Rini [this message]
2021-09-20  6:46 ` Eugen.Hristev
2021-09-20  7:12   ` Anatolij Gustschin

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=20210826124401.GH858@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=Eugen.Hristev@microchip.com \
    --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