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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 23 Nov 2020 11:44:17 +0100
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>,
        ksummit <ksummit-discuss@...ts.linuxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: at91 git tree in linux-next

Hi Stephen,

On Thu, Aug 23, 2018 at 1:31 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <nicolas.ferre@...rochip.com> wrote:
> > Alexandre Ludovic and myself are the group of maintainers for Microchip
> > ARM SoCs. The current tree that we have in linux-next is mine [1] and we
> > are moving to a common group kernel.org tree.
> >
> > So, can you please add our new tree to linux-next:
> > at91 git
> > git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
> >
> > instead of:
> > git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git#at91-next
> >
> > In addition to that, we also have now a "fixes" branch. Can you please
> > add it to your "fixes" tree?
> >
> > at91 git
> > git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes
> >
> > Thanks for your help, best regards,
> >    Nicolas
> >
> >
> > [1]
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees#n84
>
> All done.  I added Alexandre and Ludovic as contacts for both trees as
> well.

How is this working?

>From next-20201123:

    Merging at91/at91-next (0698efbb33ef Merge branches 'at91-soc',
'at91-dt' and 'at91-defconfig' into at91-next)

which is indeed a recent commit, while Next/Trees has the wrong repo
(linux-at91.git instead of linux.git):

$ git show linux-next/master:Next/Trees | grep at91
at91-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes
at91 git git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux-at91.git#at91-next
$ git ls-remote
git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux-at91.git
fatal: remote error: access denied or repository not exported:
/pub/scm/linux/kernel/git/at91/linux-at91.git

Gr{oetje,eeting}s,

                        Geert


--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ