From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Can't login to GIT
Date: Mon, 01 Nov 2021 11:39:02 +0100 [thread overview]
Message-ID: <87b63b3a-2e66-8a86-c4ef-f03afcd6aad0@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
Hi,
GIT doesn't like me anymore!?
Tried to pull 'origin next', but:
***SNIP***
mfischer(a)git.ipfire.org's password:
Permission denied, please try again.
mfischer(a)git.ipfire.org's password:
Connection closed by 81.3.27.38 port 22
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
***SNAP***
Can anyone confirm?
Best,
Matthias
next reply other threads:[~2021-11-01 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 10:39 Matthias Fischer [this message]
2021-11-01 11:00 ` Peter Müller
2021-11-01 11:01 ` Michael Tremer
2021-11-01 12:05 ` Matthias Fischer
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=87b63b3a-2e66-8a86-c4ef-f03afcd6aad0@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