git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: When will this patch be merged?
Date: Sat, 11 Apr 2020 23:31:58 -0700	[thread overview]
Message-ID: <20200412063158.GA27852@gmail.com> (raw)
In-Reply-To: <20200411120821.7675-1-lockywolf@gmail.com>

Hi Vladimir,

Vladimir Nikishkin wrote:

> [Subject: Re: When will this patch be merged?]

Please keep in mind that these mails appear in people's crowded
inboxes, where a subject line can provide valuable context.

Which patch do you mean?

> When will this patch be merged? It is 2020, and git submodule is
> barely usable with my internet provider, since outbound connections
> are randomly shaped to 10k/s. At the moment I set up updating
> submodules for the night, hoping that it works. If this patch was
> accepted I would just see at which attempt the stream is not shaped
> and reissue the command if it is.

From the In-Reply-To field, it looks like you're responding to [1]
("submodule: add verbose mode for add/update"), from 2014.  Have you
tested that patch?  Does it apply to current Git?  Has it been working
well for you?

For your application, it sounds like having a timeout (plus Git's
existing support for retries when fetching submodules) would help.  Am
I understanding correctly?

Thanks and hope that helps,
Jonathan

[1] https://lore.kernel.org/git/1394631731-4678-1-git-send-email-orgad.shaneh@audiocodes.com/

      reply	other threads:[~2020-04-12  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 13:42 [PATCH] submodule: add verbose mode for add/update Orgad Shaneh
2014-03-12 16:15 ` Jens Lehmann
2014-03-12 20:00   ` Orgad Shaneh
2020-04-11 12:08 ` When will this patch be merged? Vladimir Nikishkin
2020-04-12  6:31   ` Jonathan Nieder [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200412063158.GA27852@gmail.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lockywolf@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).