From: Sylwester Nawrocki <s.nawrocki@samsung•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: error when fetching the clk-samsung tree
Date: Mon, 4 May 2020 11:15:22 +0200 [thread overview]
Message-ID: <1ab13824-6fcc-e2fa-c2d8-3595bc070f03@samsung.com> (raw)
In-Reply-To: <20200504084835.5814c682@canb.auug.org.au>
Hi Stephen,
On 04.05.2020 00:48, Stephen Rothwell wrote:
> Fetching the clk-samsung tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk.git#for-next)
> produces the following error:
>
> fatal: couldn't find remote ref refs/heads/for-next
>
> I am using the last version I fetched (which is empty relative to Linus'
> tree).
Apologies for an oversight on my side, it should be fixed now (there will
be still no new patches comparing to Linus' tree).
--
Regards,
Sylwester
prev parent reply other threads:[~2020-05-04 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200503224848eucas1p2446520ac65d79c4a59d5665bf915f7e6@eucas1p2.samsung.com>
2020-05-03 22:48 ` linux-next: error when fetching the clk-samsung tree Stephen Rothwell
2020-05-04 9:15 ` Sylwester Nawrocki [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=1ab13824-6fcc-e2fa-c2d8-3595bc070f03@samsung.com \
--to=s.nawrocki@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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