public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>, binutils@sourceware.org
Subject: Re: where is the vcs for the binutils sourceware page?
Date: Sun, 7 Jan 2024 19:17:11 +0100	[thread overview]
Message-ID: <20240107181711.GY26453@gnu.wildebeest.org> (raw)
In-Reply-To: <7cf3aec6-8b52-4cc2-849c-14d301d74ecd@redhat.com>

Hi Nick,

On Fri, Jan 05, 2024 at 01:55:20PM +0000, 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.

Shall we setup a binutils-htdocs git repo to hold these webpages?
That is what gdb does, https://sourceware.org/cgit/gdb-htdocs/ Then
anybody who has binutils commit access can help directly and nobody
would need shell access to just update them.

Cheers,

Mark

  parent reply	other threads:[~2024-01-07 18:17 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
2024-01-07 18:17       ` Mark Wielaard [this message]
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=20240107181711.GY26453@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --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).