From: Mike Frysinger <vapier@gentoo.org>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: where is the vcs for the binutils sourceware page?
Date: Fri, 5 Jan 2024 07:50:12 -0500 [thread overview]
Message-ID: <ZZf7BEfYR2RBEyUk@vapier> (raw)
In-Reply-To: <3d1826f4-b63a-4d3c-9715-64d40c55c239@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On 05 Jan 2024 11:39, Nick Clifton wrote:
> > where is the source for the binutils sourceware page ? https://sourceware.org/binutils/
>
> It is on sourceware itself, in the /sourceware/www/sourceware/htdocs/binutils directory.
so it isn't maintained in a VCS ? only people who have (ssh?) access can
change the page ? i wanted to send patches, but it's not clear how.
> > it's not in CVS as that hasn't been updated since 2017 & binutils-2.29. sourceware.org:/cvs/binutils/htdocs
>
> Err, that directory does not appear to exist. But the sourceware binutils
> page has definitely been updated (Jul 30, 2023), and does refer to the
> 2.41 release.
$ cvs -z9 -d :ext:vapier@sourceware.org:/cvs/binutils co htdocs
...
$ cd htdocs
$ cvs log index.html
RCS file: /cvs/binutils/htdocs/index.html,v
Working file: index.html
head: 1.75
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 75; selected revisions: 75
description:
----------------------------
revision 1.75
date: 2017/07/24 10:52:27; author: gingold; state: Exp; lines: +6 -6
Update index.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-05 12:50 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 [this message]
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
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=ZZf7BEfYR2RBEyUk@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).