From: Matthias Fischer <matthias.fischer@ipfire.org>
To: "IPFire: Tremer, Michael" <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Fwd: GIT has had enough and is no longer interested. Thats it!
Date: Fri, 26 Dec 2025 20:06:08 +0100 [thread overview]
Message-ID: <c84527e0-1ec0-400c-bb07-fa952af3dbf9@ipfire.org> (raw)
In-Reply-To: <b104aacc-edf4-46b3-95c5-46b1edc7f60a@ipfire.org>
Hi Michael,
sorry for this, but since the mail below can't still be seen on the
list, I don't know if everything is working as it should - so I'm
sending it directly to you. Just FYI only... ;-)
All the best for now and the next year!
Matthias
-------- Forwarded Message --------
Subject: GIT has had enough and is no longer interested. Thats it!
Date: Fri, 26 Dec 2025 14:01:51 +0100
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: IPFire: Development-List <development@lists.ipfire.org>
Hi,
sorry to interrupt any preparations for new year, but GIT doesn't like
me (or us?) anymore:
Since two days https://git.ipfire.org/ leads to:
"Forbidden
You don't have permission to access this resource."
Just for the records... ;-)
Best regards and all the best for the new year...!
Matthias
next prev parent reply other threads:[~2025-12-26 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 13:01 Matthias Fischer
2025-12-26 19:06 ` Matthias Fischer [this message]
2025-12-26 23:31 ` Fwd: " Adolf Belka
2025-12-27 1:23 ` Matthias Fischer
2025-12-27 12:10 ` Adolf Belka
2025-12-27 13:20 ` Matthias Fischer
2025-12-28 11:23 ` Michael Tremer
2025-12-28 15:53 ` Matthias Fischer
2025-12-28 16:00 ` Michael Tremer
2025-12-28 21:17 ` Matthias Fischer
2025-12-29 14:02 ` Michael Tremer
2025-12-29 18:00 ` Charles Brown
2025-12-29 18:23 ` Charles Brown
2025-12-30 15:37 ` Matthias Fischer
2025-12-31 17:41 ` Michael Tremer
2025-12-31 18:11 ` Matthias Fischer
2025-12-31 21:15 ` Charles Brown
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=c84527e0-1ec0-400c-bb07-fa952af3dbf9@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@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