From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Sourceware / GNU Toolchain at Cauldron
Date: Mon, 3 Oct 2022 21:16:24 +0200 [thread overview]
Message-ID: <Yzs1CKZf91rtpuIK@wildebeest.org> (raw)
In-Reply-To: <20221003135317.GJ7916@redhat.com>
Hi,
On Mon, Oct 03, 2022 at 09:53:17AM -0400, Frank Ch. Eigler via Overseers wrote:
> > > We are fortunate to use fully decentralized source control systems,
> > > where full clones at developers - and at other services like github
> > > etc. - are routine, and permit work to continue. I'd be surprised to
> > > hear of any organization hoping to hurt free software development by
> > > DoS'ing the sites - it'd be a futile gesture.
> >
> > At least for GNU toolchain we have never really blessed other clones. The
> > only blessed way to get sources is via sourceware.
>
> This is easily corrected. Git mirrors at the FSF and other hosting
> systems can be stood up, today, at the projects' individual discretion.
Note that sourceware git repos have an experimental mirror on
sourcehut already
https://git.sr.ht/~sourceware/
Which can also be used to sent patches through email from the webform
as an alternative to git send-email or sending raw patches by email
https://gnu.wildebeest.org/~mark/sourceware/presentation.html#slide18
Cheers,
Mark
next prev parent reply other threads:[~2022-10-03 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 20:57 Zoë Kooyman
2022-09-16 21:10 ` Ian Kelling
2022-09-18 16:27 ` Mark Wielaard
2022-09-18 21:38 ` Mark Wielaard
2022-09-19 21:09 ` Mark Wielaard
2022-09-26 22:04 ` Carlos O'Donell
2022-09-27 1:31 ` Alexandre Oliva
2022-09-27 11:02 ` Mark Wielaard
2022-09-28 11:14 ` Frank Ch. Eigler
2022-09-30 13:38 ` Carlos O'Donell
2022-10-02 14:55 ` Frank Ch. Eigler
2022-10-03 13:26 ` Siddhesh Poyarekar
2022-10-03 13:53 ` Frank Ch. Eigler
2022-10-03 19:16 ` Mark Wielaard [this message]
2022-10-03 15:55 ` Christopher Faylor
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=Yzs1CKZf91rtpuIK@wildebeest.org \
--to=mark@klomp.org \
--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).