From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Suddenly: connection refused on 'git.ipfire.org'
Date: Sat, 05 Oct 2019 09:21:15 +0200 [thread overview]
Message-ID: <f2131ae1-001a-5407-e407-f5de17fdb5f9@ipfire.org> (raw)
In-Reply-To: <7B686C7D-85B5-4480-980B-2EB3CB6AF40E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
Hi,
On 28.09.2019 18:33, Michael Tremer wrote:
> ...
> I suppose that nobody did anything and the blocking rule has been removed automatically after a while.
Today it happened again: sending to 'patchwork' ("git send-email ...")
was ok, but in the next moment 'git' ("git push mfischer ...") doesn't
like me anymore:
***SNIP***
Password for 'smtp://mfischer(a)submissions.ipfire.org:465':
OK. Log says:
Server: submissions.ipfire.org
MAIL FROM:<matthias.fischer(a)ipfire.org>
RCPT TO:<development(a)lists.ipfire.org>
From: Matthias Fischer <matthias.fischer(a)ipfire.org>
To: development(a)lists.ipfire.org
Subject: [PATCH] unbound: Update to 1.9.4
Date: Sat, 5 Oct 2019 09:09:29 +0200
Message-Id: <20191005070929.3484-1-matthias.fischer(a)ipfire.org>
X-Mailer: git-send-email 2.18.0
Result: 250
root(a)Devel: /home/matz/ipfire-2.x # git push mfischer unbound
mfischer(a)git.ipfire.org's password:
[...long pause...]
Connection to git.ipfire.org closed by remote host.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
root(a)Devel: /home/matz/ipfire-2.x #
***SNAP***
Could someone please tell me how long "after a while" is? ;-)
Thanks in advance.
Best,
Matthias
next prev parent reply other threads:[~2019-10-05 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 18:03 Matthias Fischer
2019-09-26 18:04 ` Michael Tremer
2019-09-26 18:18 ` Matthias Fischer
2019-09-27 16:10 ` Matthias Fischer
2019-09-28 16:33 ` Michael Tremer
2019-10-05 7:21 ` Matthias Fischer [this message]
2019-10-05 10:07 ` Michael Tremer
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=f2131ae1-001a-5407-e407-f5de17fdb5f9@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox