linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error trying to fetch the scmi tree
Date: Fri, 16 Apr 2021 10:49:03 +0100	[thread overview]
Message-ID: <20210416094903.naf2uqknkk3bkqqr@bogus> (raw)
In-Reply-To: <20210416090341.25d9fca6@canb.auug.org.au>

Hi Stephen,

On Fri, Apr 16, 2021 at 09:03:41AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Fetching the scmi tree produces this error:
>
> fatal: couldn't find remote ref refs/heads/for-linux-next
>

Thanks for letting me know. No idea how, but I have messed up and managed
to push it as tag and also deleted the branch. It must be fixed now.

> I will use the scmi tree from next-20210415 for today.
>

Thanks.

--
Regards,
Sudeep

      reply	other threads:[~2021-04-16  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 23:03 linux-next: error trying to fetch the scmi tree Stephen Rothwell
2021-04-16  9:49 ` Sudeep Holla [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=20210416094903.naf2uqknkk3bkqqr@bogus \
    --to=sudeep.holla@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).