Sorry I did not see this thread until now.
Paul Eggert wrote:
> Can't browse source code via Savannah now. Here are symptoms:
A 502 Bad Gateway is a symptom of the machine being too overloaded to
process the request before the web server times out talking to the CGI
process. In this case the git
On 2025-02-02 12:21, Paul Eggert wrote:
$ wget -S -O- 'https://git.savannah.gnu.org/gitweb/?p=gettext.git'
This worked for me just now.
It works for me now too.
Now it's failing, with different symptoms:
$ wget -S -O- 'https://git.savannah.gnu.org/gitweb/?p=gettext.git'
--2025-02-02 19
On 2025-02-02 12:03, Corwin Brust wrote:
Would you be able to try again using the git:// version of the incantation?
Plain git was working at the time. (wget doesn't grok "git://".)
Browsing via the Savannah web didn't work. The not-working was for some
time (a few minutes? don't recall exact
Would you be able to try again using the git:// version of the incantation?
It's a bit less resource intensive on our side; anyone with commit to
some project should be able to do an "authenticated clone" of any
other project (using the same savannah account).
On Sun, Feb 2, 2025 at 12:32 PM Paul
Can't browse source code via Savannah now. Here are symptoms:
$ wget -S -O- 'https://git.savannah.gnu.org/gitweb/?p=gettext.git'
--2025-02-02 10:31:43-- https://git.savannah.gnu.org/gitweb/?p=gettext.git
Resolving git.savannah.gnu.org (git.savannah.gnu.org)... 209.51.188.78,
2001:470:142:6::78
