ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] at91 git tree in linux-next
Date: Mon, 23 Nov 2020 11:44:17 +0100	[thread overview]
Message-ID: <CAMuHMdUkQqJ_+8xy3q7tjCXCU4cZsnT7EOHtfTDroc4Ke0yPrw@mail.gmail.com> (raw)
In-Reply-To: <20180823093045.00e751b0@canb.auug.org.au>

Hi Stephen,

On Thu, Aug 23, 2018 at 1:31 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <nicolas.ferre@microchip.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@linux-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
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  reply	other threads:[~2020-11-23 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551A9FAC.2010203@atmel.com>
2018-08-22 12:47 ` Nicolas Ferre
2018-08-22 23:30   ` Stephen Rothwell
2020-11-23 10:44     ` Geert Uytterhoeven [this message]
2020-11-23 11:59       ` Stephen Rothwell

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=CAMuHMdUkQqJ_+8xy3q7tjCXCU4cZsnT7EOHtfTDroc4Ke0yPrw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=sfr@canb.auug.org.au \
    /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