From: Mark Wielaard <mark@klomp.org>
To: Nick Clifton via Overseers <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>, Nick Clifton <nickc@redhat.com>
Subject: Re: sftp access for binutils
Date: Thu, 15 Feb 2024 01:26:10 +0100 [thread overview]
Message-ID: <20240215002610.GA29401@gnu.wildebeest.org> (raw)
In-Reply-To: <05dbaf0a-d95b-4bda-81bb-5a3b93c99484@redhat.com>
Hi Nick,
On Fri, Feb 09, 2024 at 11:22:05AM +0000, Nick Clifton via Overseers wrote:
> >Note that for the websites update we want to setup a binutils-htdoc.git
> >repo like other sourceware projects have so that you can just update
> >the website through git:
> >https://inbox.sourceware.org/binutils/a3ecae09-2858-4b60-9fd0-6c0618c51424@redhat.com/
> >
> >But I didn't want to do this switch in the middle of a release. With
> >the 2.42 release out the door, now might be a good time to do that. But
> >please let me know if you first want to do some website updates the
> >old-fashion way.
>
> I think that now would be a really good time to set this up, if you
> don't mind. Thanks.
Done using the guide at
https://sourceware.org/sourceware-wiki/OSNewWebHosting/
There is now a binutils-htdocs git repo which can be updated by anyone
in the binutils group (note that is a smaller group of people than
have access to the binutils-gdb repo, which is the src group, so
original gdb hackers cannot).
Any update to binutils-htdocs should show up under
https://sourceware.org/binutils/
Unfortunately I couldn't get all history. There are only the original
cvs commits from 1999 to 2017. Everything after I had to update by
hand.
There is also a cgit index: https://sourceware.org/cgit/binutils-htdocs/
Please let us know if anything doesn't work as intended.
Cheers,
Mark
next prev parent reply other threads:[~2024-02-15 0:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:48 Jose E. Marchesi
2024-01-29 16:23 ` Frank Ch. Eigler
2024-01-29 16:25 ` Jose E. Marchesi
2024-01-29 16:59 ` Mark Wielaard
2024-02-09 11:22 ` Nick Clifton
2024-02-15 0:26 ` Mark Wielaard [this message]
2024-02-16 10:32 ` Nick Clifton
2024-02-16 10:37 ` Mark Wielaard
2024-02-16 11:37 ` Nick Clifton
2024-02-16 11:39 ` Frank Ch. Eigler
2024-02-16 11:32 ` Frank Ch. Eigler
2024-02-16 11:34 ` Nick Clifton
2024-02-16 12:14 ` Nick Clifton
2024-02-10 7:30 石沒用
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=20240215002610.GA29401@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=nickc@redhat.com \
--cc=overseers@sourceware.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).