linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: error while fetching the ipvs-next tree
@ 2023-03-08 21:54 Stephen Rothwell
  2023-03-09  5:51 ` Simon Horman
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2023-03-08 21:54 UTC (permalink / raw)
  To: Simon Horman; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

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

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?

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: error while fetching the ipvs-next tree
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Simon Horman @ 2023-03-09  5:51 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Simon Horman, Linux Kernel Mailing List, Linux Next Mailing List

Hi Stephen,

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.

Kind regards,
Simon


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: error while fetching the ipvs-next tree
  2023-03-09  5:51 ` Simon Horman
@ 2023-03-09  7:34   ` Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2023-03-09  7:34 UTC (permalink / raw)
  To: Simon Horman
  Cc: Simon Horman, Linux Kernel Mailing List, Linux Next Mailing List

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-03-09  7:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).