lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230309183402.21420df2@canb.auug.org.au>
Date:   Thu, 9 Mar 2023 18:34:02 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Simon Horman <horms@...nel.org>
Cc:     Simon Horman <horms@...ge.net.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: error while fetching the ipvs-next tree

Hi Simon,

On Thu, 9 Mar 2023 06:51:35 +0100 Simon Horman <horms@...nel.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

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ