From: "Richard Earnshaw \(lists\) via Gdb" <gdb@sourceware.org>
To: David Malcolm <dmalcolm@redhat.com>,
Mark Wielaard <mark@klomp.org>,
binutils@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org,
newlib@sourceware.org, libc-alpha@sourceware.org
Cc: forge@sourceware.org
Subject: Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)
Date: Thu, 24 Oct 2024 16:36:07 +0100 [thread overview]
Message-ID: <998c2aaa-99d0-421b-9c94-ee727856f432@arm.com> (raw)
In-Reply-To: <66e3991c177fac91ca64fce1b035171156a73e79.camel@redhat.com>
On 24/10/2024 16:29, David Malcolm 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?
>
> GCC has its own short notation for referring to commits, see e.g.
>
> https://forge.sourceware.org/gcc/gcc-mirror/commit/83abdb041426b7490e93c3f77be93148bcd94de3
> where I wrote:
> "I believe this hasn't been necessary since r15-1413-gd3878c85f331c7."
> It would be nice if the "r15-1413-gd3878c85f331c7" were to get auto-
> urlified in the web UI to
> https://forge.sourceware.org/gcc/gcc-mirror/commit/d3878c85f331c7
>
> Similarly, in GCC we use the notation PRnnnnnn or PR component/nnnnnn
> to refer to "problem reports" in bugzilla. Looking at e.g.
> https://forge.sourceware.org/gcc/gcc-mirror/commit/65c5bbe1c92f9c08e99d3a37c136f2ef9804a37f
> it would be nice if the "PR114423" in the subject line and the
> "PR preprocessor/114423" in the ChangeLog fragments in the commit log
> got auto-urlified in the web UI to:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114423
>
See the wiki page I added today for setting up bugzilla (gcc.gnu.org/wiki/ForgeExperiment). It only works for the <component>/<id> style due to limitations in the way forgejo uses the regex groups.
> Other projects sharing the forgejo instance have other notations,
> policies, and bug tracker instances, of course.
>
> FWIW I seem to recall seeing something like this working in the
> instance that was recently demoed at Cauldron.
>
> Hope this is constructive; thanks again
> Dave
>
next prev parent reply other threads:[~2024-10-24 15:40 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 [this message]
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
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=998c2aaa-99d0-421b-9c94-ee727856f432@arm.com \
--to=gdb@sourceware.org \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=dmalcolm@redhat.com \
--cc=forge@sourceware.org \
--cc=gcc@gcc.gnu.org \
--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