All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Michal Hocko <mhocko@kernel.org>
Cc: Qian Cai <cai@lca.pw>, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org
Subject: Re: git.cmpxchg.org/linux-mmots.git repository corruption?
Date: Tue, 10 Sep 2019 12:33:57 +0300	[thread overview]
Message-ID: <20190910093357.zoidae3j5nyy5g2v@box.shutemov.name> (raw)
In-Reply-To: <20190910070720.GF2063@dhcp22.suse.cz>

On Tue, Sep 10, 2019 at 09:07:20AM +0200, Michal Hocko wrote:
> On Mon 09-09-19 16:56:33, Qian Cai wrote:
> > On Mon, 2019-09-09 at 09:59 -0400, Qian Cai wrote:
> > > Tried a few times without luck. Anyone else has the same issue?
> > > 
> > > # git clone git://git.cmpxchg.org/linux-mmots.git
> > > Cloning into 'linux-mmots'...
> > > remote: Enumerating objects: 7838808, done.
> > > remote: Counting objects: 100% (7838808/7838808), done.
> > > remote: Compressing objects: 100% (1065702/1065702), done.
> > > remote: aborting due to possible repository corruption on the remote side.
> > > fatal: early EOF
> > > fatal: index-pack failed
> > 
> > It seems that it is just the remote server is too slow. Does anyone consider
> > moving it to a more popular place like git.kernel.org or github etc?
> 
> Andrew was considering about a git tree for mm patches earlier this
> year. But I am not sure it materialized in something. Andrew? poke poke
> ;)

Johannes, maybe it's time to move these trees to git.kernel.org?

-- 
 Kirill A. Shutemov


  reply	other threads:[~2019-09-10  9:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 13:59 git.cmpxchg.org/linux-mmots.git repository corruption? Qian Cai
2019-09-09 20:56 ` Qian Cai
2019-09-10  7:07   ` Michal Hocko
2019-09-10  9:33     ` Kirill A. Shutemov [this message]
2019-09-10 14:30       ` Johannes Weiner
2019-09-16 13:43         ` Johannes Weiner
2019-09-16 14:14           ` Kirill A. Shutemov
2019-09-17  8:17           ` David Hildenbrand

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=20190910093357.zoidae3j5nyy5g2v@box.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=cai@lca.pw \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.