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 10:06:59 -0500 [thread overview]
Message-ID: <ZZgbE-2BRXJZ8eeX@vapier> (raw)
In-Reply-To: <7cf3aec6-8b52-4cc2-849c-14d301d74ecd@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On 05 Jan 2024 13:55, Nick Clifton wrote:
> >> It is on sourceware itself, in the /sourceware/www/sourceware/htdocs/binutils directory.
> >
> > so it isn't maintained in a VCS ?
>
> Sorry, no. :-(
>
> > only people who have (ssh?) access can change the page ?
>
> Directly yes. Of course others can always ask to have changes made.
>
> > i wanted to send patches, but it's not clear how.
>
> 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.
>
> >>> 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.
> > $ cvs -z9 -d :ext:vapier@sourceware.org:/cvs/binutils co htdocs
>
> I stand corrected.
>
> But that is definitely the old version of the docs, before the switch
> from cvs to git.
sorry i'm not following here. you said it's not maintained in a VCS, but
then you talk about switching from cvs to git. or did you mean the main
binutils-gdb.git project and not htdocs ? the cvs htdocs was basically
abandoned when the main source tree switched from cvs to git ?
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-05 15:07 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 [this message]
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=ZZgbE-2BRXJZ8eeX@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).