From: Jan Kara <jack@suse•cz>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Jan Kara <jack@suse•cz>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: error fetching the vfs-jk tree
Date: Tue, 14 Nov 2017 10:00:37 +0100 [thread overview]
Message-ID: <20171114090037.GA7053@quack2.suse.cz> (raw)
In-Reply-To: <20171114094010.5601ee2c@canb.auug.org.au>
Hi,
On Tue 14-11-17 09:40:10, Stephen Rothwell wrote:
> Fetching the vfs-jk tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git#vfs)
> produces this error:
>
> fatal: Couldn't find remote ref refs/heads/vfs
>
> Do you want me to still fetch/merge that tree?
Sorry, I forgot you were still fetching it. No, there's no need to fetch
that branch anymore (it was a branch for one time work and I've deleted it
now since it was untouched for an year or so). Thanks!
Honza
--
Jan Kara <jack@suse•com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-11-14 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 22:40 linux-next: error fetching the vfs-jk tree Stephen Rothwell
2017-11-14 9:00 ` Jan Kara [this message]
2017-11-14 10:31 ` 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=20171114090037.GA7053@quack2.suse.cz \
--to=jack@suse$(echo .)cz \
--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