From: Stephen Rothwell <sfr@canb•auug.org.au>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Matthias Brugger <matthias.bgg@gmail•com>
Subject: Re: MediaTek for-next: Replace matthias.bgg tree with mediatek
Date: Wed, 7 Feb 2024 09:05:05 +1100 [thread overview]
Message-ID: <20240207090505.515d8977@canb.auug.org.au> (raw)
In-Reply-To: <00a81be6-7dd7-4959-b1dc-eb94022bf0e5@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Hi Angelo,
On Tue, 6 Feb 2024 11:08:25 +0100 AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel•org> wrote:
>
> A while ago we migrated the MediaTek SoC trees from Matthias' GIT repo to the new
> MediaTek collaborative one. I just noticed that the linux-next branch didn't get
> replaced (we didn't tell you anything about it, so that's our bad!).
>
> Can you please replace the tracked for-next branch?
>
> ...The old one, to remove, is:
> git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git#for-next
>
> ...the new one, to add, is:
> git://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git#for-next
Done.
I have only Matthias listed as a contact for that tree, should I add anyone
else?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-06 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:08 MediaTek for-next: Replace matthias.bgg tree with mediatek AngeloGioacchino Del Regno
2024-02-06 22:05 ` Stephen Rothwell [this message]
2024-02-07 16:08 ` Matthias Brugger
2024-02-07 20:02 ` Stephen Rothwell
2024-02-08 9:07 ` AngeloGioacchino Del Regno
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=20240207090505.515d8977@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=angelogioacchino.delregno@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthias.bgg@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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