public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Jose E. Marchesi via Overseers" <overseers@sourceware.org>,
	"Frank Ch. Eigler" <fche@elastic.org>
Cc: "Jose E. Marchesi" <jemarch@gnu.org>, Nick Clifton <nickc@redhat.com>
Subject: Re: sftp access for binutils
Date: Mon, 29 Jan 2024 17:59:09 +0100	[thread overview]
Message-ID: <6a1677dbf543a3626dd7811ce7423449ba4a5ff6.camel@klomp.org> (raw)
In-Reply-To: <87bk94p0mo.fsf@gnu.org>

Hi Jose,

On Mon, 2024-01-29 at 17:25 +0100, Jose E. Marchesi via Overseers
wrote:
> > > I am helping Nick with the binutils releases, and I would need sftp
> > > access to sourceware in order to update webpages and upload tarballs.
> > 
> > Upgraded your account from rash to bash.  Enjoy carefully.
> 
> Thank you Frank.
> Tried with sftp and it worked.

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.

Cheers,

Mark

  reply	other threads:[~2024-01-29 16:59 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 [this message]
2024-02-09 11:22       ` Nick Clifton
2024-02-15  0:26         ` Mark Wielaard
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=6a1677dbf543a3626dd7811ce7423449ba4a5ff6.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=fche@elastic.org \
    --cc=jemarch@gnu.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).