git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jakobus Schürz" <wertstoffe@nurfuerspam.de>
Cc: git@vger.kernel.org
Subject: Re: ls-remote set timeout
Date: Mon, 18 Mar 2019 11:34:22 +0900	[thread overview]
Message-ID: <xmqqbm287vwx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <0Mey7N-1hOXHn3kBF-00OYB8@mail.gmx.com> ("Jakobus Schürz"'s message of "Thu, 14 Mar 2019 10:38:01 +0100")

Jakobus Schürz <wertstoffe@nurfuerspam.de> writes:

> Does anyone has an idea?

Lack of response generally indicate that people are not interested
but the reason why they are not varies.  It may be because you did
not give them sufficient information about your situation (are you
trying to do this on Windows, for example?).  It may be because you
are looking for a solution that applies only to a narrow situation
that they are not interested in, but by stepping back a bit and by
coming up with a solution that may apply to more general problem may
pique their interest.

Instead of patching "git" to tell it what the connection timeout is,
perhaps a more general command that runs anything and aborts it if
it does not finish within given time period, e.g.

	timeout 180 git ls-remote <REMOTE>

may run "git ls-remote <REMOTE>" but kill it if it does not finish
within 180 seconds.

If you wrote such a general purpose command, that would help you
running ls-remote and abort it if it does not finish within the
given timeout, and also help others who are not using Git but with a
similar need to run other things and kill them when they run for too
long.

Who knows.  If you look for such a command, you might find that one
already exists.  http://lmgtfy.com/?q=run+linux+command+with+timeout

      reply	other threads:[~2019-03-18  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08  9:31 ls-remote set timeout Jakobus Schürz
2019-03-14  9:38 ` Jakobus Schürz
2019-03-18  2:34   ` Junio C Hamano [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=xmqqbm287vwx.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=wertstoffe@nurfuerspam.de \
    /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).