From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro•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 drm-msm-lumag tree
Date: Fri, 26 Apr 2024 11:36:25 +1000 [thread overview]
Message-ID: <20240426113625.5b97c03d@canb.auug.org.au> (raw)
In-Reply-To: <CAA8EJprYTKSwS+r+u3yVbo7cLVkA+XnBT9UHVt+yM4Qp3u-GnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Hi Dmitry,
On Fri, 26 Apr 2024 04:26:26 +0300 Dmitry Baryshkov <dmitry.baryshkov@linaro•org> wrote:
>
> On Fri, 26 Apr 2024 at 03:46, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Fetching the drm-msm-lumag tree produced this error:
> >
> > fatal: couldn't find remote ref refs/heads/msm-next-lumag
>
> Should be fixed now
Yes, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-04-26 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 0:46 linux-next: error fetching the drm-msm-lumag tree Stephen Rothwell
2024-04-26 1:26 ` Dmitry Baryshkov
2024-04-26 1:36 ` Stephen Rothwell [this message]
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=20240426113625.5b97c03d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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