linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simon Horman <horms@kernel.org>
Cc: Simon Horman <horms@verge.net.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error while fetching the ipvs-next tree
Date: Thu, 9 Mar 2023 18:34:02 +1100	[thread overview]
Message-ID: <20230309183402.21420df2@canb.auug.org.au> (raw)
In-Reply-To: <ZAlz581aBJewZLw3@kernel.org>

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

Hi Simon,

On Thu, 9 Mar 2023 06:51:35 +0100 Simon Horman <horms@kernel.org> wrote:
>
> On Thu, Mar 09, 2023 at 08:54:15AM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Attempting to fetch the ipvs-next tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git#master)
> > today produces this error:
> > 
> > fatal: couldn't find remote ref refs/heads/master
> > 
> > Should I switch to using the "main" branch?
> > 
> > I also notice thet the ipvs tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git) has both a
> > "master" and "main" branch.  Should I be using "main" there as well?  
> 
> Sorry for not letting you know in advance.
> 
> Yes, please use main for both the ipvs-next and ipvs trees.
> 
> I plan to remove master from the ipvs tree too.

OK, I have switched both over.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-03-09  7:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 21:54 linux-next: error while fetching the ipvs-next tree Stephen Rothwell
2023-03-09  5:51 ` Simon Horman
2023-03-09  7:34   ` Stephen Rothwell [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=20230309183402.21420df2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=horms@kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).