Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonathan Wakely via Gdb <gdb@sourceware.org>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
	binutils@sourceware.org, gcc@gcc.gnu.org,  gdb@sourceware.org,
	newlib@sourceware.org, libc-alpha@sourceware.org,
	 forge@sourceware.org
Subject: Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)
Date: Thu, 24 Oct 2024 16:42:17 +0100	[thread overview]
Message-ID: <CAH6eHdQRC3BwB6TVqpePW=dAqyN6PFAAwEx=C1_O54LykzV_Cg@mail.gmail.com> (raw)
In-Reply-To: <66e3991c177fac91ca64fce1b035171156a73e79.camel@redhat.com>

On Thu, 24 Oct 2024 at 16:29, David Malcolm <dmalcolm@redhat.com> wrote:

> On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard 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). Some
> > things haven't been setup yet (external trackers/bugzilla, incoming
> > email, ci, etc.)
> >
> > The full setup can be found in this git repository:
> > https://sourceware.org/cgit/forge/
> >
> > For now it is only open for existing maintainers/developers for
> > experimentating with a pull-request model. We can add others as long
> > as they understand this is an experiment and does not mean projects
> > are accepting patches through it. Contributions should still be sent
> > through the mailinglists.
> >
> > 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.
> >
> > https://sourceware.org/mailman/listinfo/forge
>
> Thanks for setting this up.
>
> How easy would it be to set up automatic URL generation in the web UI
> from regexes on the text of commit subjects/message?
>

Currently not possible, but there's an upstream feature request to support
it:
https://codeberg.org/forgejo/forgejo/issues/3274

  parent reply	other threads:[~2024-10-24 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  1:22 Sourceware forge experiment 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 [this message]
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
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='CAH6eHdQRC3BwB6TVqpePW=dAqyN6PFAAwEx=C1_O54LykzV_Cg@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=dmalcolm@redhat.com \
    --cc=forge@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.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