Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org,
	 newlib@sourceware.org, libc-alpha@sourceware.org,
	forge@sourceware.org
Subject: Re: Sourceware forge experiment
Date: Fri, 08 Nov 2024 14:07:54 +0100	[thread overview]
Message-ID: <fa28109239a5d4df1c267cbfc448806f8c833766.camel@klomp.org> (raw)
In-Reply-To: <CAMfHzOu83FihjWQ0bkFVN8QxQnbUi=BwmKdo8npCXQWnYSLZAw@mail.gmail.com>

Hi Eric,

On Thu, 2024-10-24 at 15:44 -0400, Eric Gallager wrote:
> On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard <mark@klomp.org> wrote:
> > As an experiment Sourceware is now running an forgejo v9 instance at
> > https://forge.sourceware.org
> > 
> > Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address
> > can register an account (please use the same user name as your account
> > name).
> > 
> > The setup has disabled most "extras" (no badges, stars, issues, wikis,
> > packages, timetracking, milestones, etc.). And users can only fork
> > existing repos (it has mirrors of various sourceware projects).
> 
> Is the intent to get mirrors of all of them on there at some point?
> I'm only seeing a few at the moment...

To see how well it scales a couple more sourceware projects now have a
mirror on the forge: https://forge.sourceware.org/explore/organizations
gcc, binutils-gdb, glibc, elfutils, newlib, valgrind, debugedit,
bunsen, annobin, bzip2, cgen, dwz, insight, libabigail and systemtap.

If you are interested in others, please just ask.
https://sourceware.org/projects.html

> > There is also a new mailinglist for discussion about the setup and the
> > best way to create a pull-request workflow. Please subscribe if you
> > create an account and mention which project/organization you would
> > like do some experiments for. We can then add you to that organization.
> > 
> 
> ...is subscribing necessary? I'm trying to limit my subscriptions...
> 
> > https://sourceware.org/mailman/listinfo/forge

It isn't necessary, but it is a good place to discuss the forge
experiment. You don't have to be subscribed to post and you can read
the archives through https://inbox.sourceware.org/forge (also through
nntp, imap, atom or git cloning the whole thing).

Cheers,

Mark

  parent reply	other threads:[~2024-11-08 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  1:22 Mark Wielaard
2024-10-24 15:29 ` Automatic URLs in forgejo? (was Re: Sourceware forge experiment) David Malcolm via Gdb
2024-10-24 15:36   ` Richard Earnshaw (lists) via Gdb
2024-10-24 15:42   ` Jonathan Wakely via Gdb
2024-10-24 15:43     ` Jonathan Wakely via Gdb
2024-10-24 19:44 ` Sourceware forge experiment Eric Gallager via Gdb
2024-10-24 20:02   ` Jonathan Wakely via Gdb
2024-11-08 13:07   ` Mark Wielaard [this message]
2024-10-24 20:25 ` Andrew Pinski via Gdb
2024-10-24 20:29   ` Andrew Pinski via Gdb

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=fa28109239a5d4df1c267cbfc448806f8c833766.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=egall@gwmail.gwu.edu \
    --cc=forge@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=newlib@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