From: Linus Torvalds <torvalds@linux-foundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] UBI/UBIFS updates for 5.1-rc1
Date: Tue, 12 Mar 2019 15:18:23 -0700 [thread overview]
Message-ID: <CAHk-=wixZBzR5nbPZ3Y1=VahyVDsqVZhRfRhewJybx2-yA_FEQ@mail.gmail.com> (raw)
In-Reply-To: <6283638.XALati16HY@blindfold>
On Tue, Mar 12, 2019 at 8:13 AM Richard Weinberger <richard@nod.at> wrote:
>
> git://git.infradead.org/linux-ubifs.git tags/upstream-5.1-rc1
Pulling this thing is taking forever for me. I can _ping_ the site,
but the "git pull" has been hanging for a while.
I really tjhink people need to stop using infradead.org for git
hosting. It really is annoyingly slow.
If you don't have a kernel.org account, use github or gitlab or
something. But use something that isn't excruciatingly slow, ok?
I don't know _why_ infradead.org is so slow, and I don't much care.
It doesn't seem to be due to network issues, because quick look at
things, there's no real network traffic, it's just waiting for the
server to start sending git object information. And git tends to be
good about network bandwidth anyway. But git *does* require some
reasonable server-side resources, and they seem to be lacking in this
case.
Linus
next prev parent reply other threads:[~2019-03-12 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:13 [GIT PULL] UBI/UBIFS updates for 5.1-rc1 Richard Weinberger
2019-03-12 22:18 ` Linus Torvalds [this message]
2019-03-12 23:40 ` Linus Torvalds
2019-03-13 8:29 ` Richard Weinberger
2019-03-13 16:50 ` pr-tracker-bot
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='CAHk-=wixZBzR5nbPZ3Y1=VahyVDsqVZhRfRhewJybx2-yA_FEQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).