From: Adolf Belka <adolf.belka@ipfire.org>
To: Matthias Fischer <matthias.fischer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Fwd: GIT has had enough and is no longer interested. Thats it!
Date: Sat, 27 Dec 2025 13:10:54 +0100 [thread overview]
Message-ID: <a065aa9b-daee-454f-a33f-ec24953b8bfd@ipfire.org> (raw)
In-Reply-To: <a6e2c947-dbf9-482d-ac8c-4c6485084eae@ipfire.org>
Hi Matthias,
Only thing I can think of is that there was a problem, which got fixed
or resolved itself but you have the faulty connection now in your
browser cache.
Maybe try clearing your browser cache and try again.
If that doesn't work, I don't have any other thoughts right now. You
will then have to wait for a response from Michael or Rico.
Regards,
Adolf.
On 27/12/2025 02:23, Matthias Fischer wrote:
> On 27.12.2025 00:31, Adolf Belka wrote:
>> Hi Matthias,
> Hallo Adolf, ;-)
>
> see my comments below...
>
>> On 26/12/2025 20:06, Matthias Fischer wrote:
>>> 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... ;-)
>> I can see both of your mails on the development list.
> I can see none of mine.
>
>>> 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."
>> I am getting access to the git repo via your link without any of those
>> warning messages.
> Hm. I still have "no permission to access this resource".
>
>> Either the problem has been fixed or you are experiencing an issue not
>> related to the infrastructure itself. Hopefully it is the former.
> Nope. No change.
>
> I'll wait. New year, new luck. It won't be long now...
>
> Best
> Matthias
>
>> Guten Rutsch.
> Danke - ebenso! ;-)
>
>> Adolf.
>>> Just for the records... ;-)
>>>
>>> Best regards and all the best for the new year...!
>>>
>>> Matthias
>>>
>>>
>
--
Sent from my laptop
next prev parent reply other threads:[~2025-12-27 12:11 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 ` Fwd: " Matthias Fischer
2025-12-26 23:31 ` Adolf Belka
2025-12-27 1:23 ` Matthias Fischer
2025-12-27 12:10 ` Adolf Belka [this message]
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=a065aa9b-daee-454f-a33f-ec24953b8bfd@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=matthias.fischer@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