From: Nick Clifton <nickc@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: binutils@sourceware.org
Subject: Re: where is the vcs for the binutils sourceware page?
Date: Mon, 8 Jan 2024 10:13:21 +0000 [thread overview]
Message-ID: <78e37e74-e463-42c6-affb-dd7eaaac17fc@redhat.com> (raw)
In-Reply-To: <ZZoQbzQh1ojvdGgQ@vapier>
Hi Mike,
>> My suggestion - post your patchess to this list as if they were a
>> change to the sources. If approved - or no-one objects - apply them
>> to the sourceware repository and ask the FSF webmasters to clone the
>> change on their copy of the page.
>
> the FSF webmasters manage sourceware.org pages ?
No...
> i thought they only managed the gnu.org pages.
Right - and since I am unable to access the FSF pages directly
I ask the FSF webmasters to make any changes for me. (For the
record they have always been very quick and helpful in responding
to my requests).
> or would it be overseers ?
Well they have the final word on the sourceware webpages.
> i noticed that the 2.33 docs are broken atm for instance:
> https://sourceware.org/binutils/docs-2.33/ -> HTTP/403
Yes, that appears to be an empty directory. I am not sure why.
There is however a point release that does work:
https://sourceware.org/binutils/docs-2.33.1/
Cheers
Nick
next prev parent reply other threads:[~2024-01-08 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 1:36 Mike Frysinger
2024-01-05 11:39 ` Nick Clifton
2024-01-05 12:50 ` Mike Frysinger
2024-01-05 13:55 ` Nick Clifton
2024-01-05 15:06 ` Mike Frysinger
2024-01-05 16:15 ` Nick Clifton
2024-01-07 2:46 ` Mike Frysinger
2024-01-08 10:13 ` Nick Clifton [this message]
2024-01-07 18:17 ` Mark Wielaard
2024-01-08 10:07 ` Nick Clifton
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=78e37e74-e463-42c6-affb-dd7eaaac17fc@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).