From: Tom Rini <trini@konsulko.com>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: u-boot@lists.denx.de, u-boot-board-maintainers@lists.denx.de,
u-boot-custodians@lists.denx.de
Subject: Re: [ANN] Updating branching scheme to use "main"
Date: Thu, 23 Jul 2026 10:46:27 -0600 [thread overview]
Message-ID: <20260723164627.GC749385@bill-the-cat> (raw)
In-Reply-To: <87qzkuqfvr.fsf@rasmusvillemoes.dk>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
On Thu, Jul 23, 2026 at 10:17:28AM +0200, Rasmus Villemoes wrote:
> On Sun, Jul 19 2026, "Tom Rini" <trini@konsulko.com> wrote:
>
> > On Wed, Jul 08, 2026 at 10:19:45AM -0600, Tom Rini wrote:
> >
> >> Hey all,
> >>
> >> As part of migrating from source.denx.de and over to
> >> git.u-boot-project.org, I think it's time to change the branching scheme
> >> from master or next to main or next. Since we'll be changing the URLs, I
> >> don't think we need to (and I'm not sure we can automatically) have a
> >> period where both exist. Thanks!
> >
> > This is now in effect. The "main" branch on
> > https://git.u-boot-project.org/u-boot/u-boot is up to date, and the
> > "master" branch (per Marek's suggestion) is on v2026.07. The GitHub,
> > Gitlab.com and also source.denx.de repositories match this.
>
> Tip: If, like me, you are heavily relying on tab-completion, you will
> now experience that
>
> git log up<TAB>m<TAB>
>
> no longer tab-completes to upstream/master, nor, as it now should,
> upstream/main, because both exist, so it only ends up showing
> "upstream/ma".
>
> You can easily configure git to ignore the "master" branch on the
> upstream remote. First, delete the current remote-tracking branch:
>
> git branch --remote --delete upstream/master
>
> Then in your repository's .git/config, make sure the remote.upstream
> section is something like
>
> [remote "upstream"]
> url = https://git.u-boot-project.org/u-boot/u-boot.git
> fetch = +refs/heads/*:refs/remotes/upstream/*
> fetch = ^refs/heads/master
>
> i.e. add the negative refspec '^refs/heads/master'. Then "git remote
> update", "git fetch upstream" and similar won't create that
> remote-tracking branch again.
>
> (Of course, replace "upstream" by "origin" or whatever your remote name
> is for the upstream repository.)
That's a good tip, thank you! It should probably get put in a doc
somewhere for others to reference. I'll try and remember that as part of
also needing to likely update some other docs.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-07-23 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 16:19 [ANN] Updating branching scheme to use "main" Tom Rini
2026-07-15 16:22 ` Marek Vasut
2026-07-15 17:01 ` Tom Rini
2026-07-15 17:42 ` Marek Vasut
2026-07-19 18:22 ` Tom Rini
2026-07-23 8:17 ` Rasmus Villemoes
2026-07-23 16:46 ` Tom Rini [this message]
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=20260723164627.GC749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=rv@rasmusvillemoes.dk \
--cc=u-boot-board-maintainers@lists.denx.de \
--cc=u-boot-custodians@lists.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