2016-11-29 23:55 GMT+02:00 Jeff King <peff@xxxxxxxx>: > On Mon, Nov 28, 2016 at 10:34:51PM +0200, Dāvis Mosāns wrote: > >> I'm trying to fetch a remote repository over https but sadly it >> timeouts too soon. >> >> $ git fetch -v upstream >> POST git-upload-pack (gzip 1148 to 641 bytes) >> POST git-upload-pack (gzip 1148 to 644 bytes) >> [...] >> Is there some way to fetch partially by smaller chunks and then repeat >> that again till everything is fetched? > > Not an easy one. The series of POSTs is an indication that the fetch > negotiation is going on for a long time, which probably means you have a > lot of commits in your local repository that aren't in the remote, or > vice versa. > > Here are the things I might try: > > - git v2.10.2 has commit 06b3d386e (fetch-pack: do not reset in_vain > on non-novel acks, 2016-09-23), which may help with this. > That output and this is already with git v2.10.2 > - HTTP, because the server is stateless, performs less well than other > protocols. If you can fetch over ssh or git://, it will probably > just work. > It's only available under https://git.replicant.us/replicant/frameworks_base.git > - If this is a one-time thing to fetch unrelated history from another > repository, you can "clone --mirror" instead of fetching, > then fetch from the mirror locally. Subsequent fetches should be > fast. > Looks like something is wrong with their server/setup since currently even clone doesn't work for me. Cloning into bare repository 'frameworks_base.git'... remote: Counting objects: 739930, done. remote: Compressing objects: 100% (196567/196567), done. error: RPC failed; curl 18 transfer closed with outstanding read data remaining fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed But someone have made a mirror for it and there clone works only still same issue with fetch. Once I will have this cloned I will try local fetch. Thanks!