From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error fetching the arm-soc-fixes tree
Date: Fri, 24 Mar 2023 15:43:30 +0700 [thread overview]
Message-ID: <ZB1ish+j4oDkbduT@debian.me> (raw)
In-Reply-To: <20230324160222.000aad9a@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
On Fri, Mar 24, 2023 at 04:02:22PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Fetching the arm-soc-fixes tree produces the following error:
>
> fatal: couldn't find remote ref refs/heads/arm/fixes
>
> This has been happening for the past few days.
I guess the tree should have been
git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git soc/fixes .
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-24 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 5:02 linux-next: error fetching the arm-soc-fixes tree Stephen Rothwell
2023-03-24 8:43 ` Bagas Sanjaya [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-11 20:41 Stephen Rothwell
2022-01-23 20:45 ` Stephen Rothwell
2021-03-08 7:57 Stephen Rothwell
2021-03-15 21:43 ` Stephen Rothwell
2021-03-18 22:55 ` Arnd Bergmann
2021-03-18 23:23 ` 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=ZB1ish+j4oDkbduT@debian.me \
--to=bagasdotme@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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;
as well as URLs for NNTP newsgroup(s).