From: Carlos O'Donell <carlos@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: gti-tac@lists.linuxfoundation.org
Subject: Re: GTI TAC Meeting Notes 2023-06-08
Date: Thu, 9 Mar 2023 23:50:51 -0500 [thread overview]
Message-ID: <83b7663a-114d-6fcd-6a62-ed3e79ba65bb@redhat.com> (raw)
In-Reply-To: <20230308192923.tuxd3ocrbg3dwqf3@nitro.local>
On 3/8/23 14:29, Konstantin Ryabitsev wrote:
> On Wed, Mar 08, 2023 at 11:44:47AM -0500, Carlos O'Donell wrote:
>> - Carlos: Where does the complexity come from?
>> - Jeff: Mailing list from bugzilla integration. Lots of custom stuff.
>
> Can someone pass me the details of this integration? I'm currently working on
> bugzilla mailing list integration via lore.kernel.org and I can see if this is
> something I'm already handling.
We haven't finished the gcc service enumeration yet, it's the last project remaining.
We will dig into this and provide you with the details as part of that enumeration.
Off the top of my head:
Normal Bugzilla behaviour:
- Bugzilla issue updates go to the mailing list.
- Email responses to the mailing list messages go back to the referenced bug.
Customization:
- gcc refs/meta/config project.config used to store customization data.
- git commit hooks used to:
- Send email to mailing list.
- Update bugzilla if issues referenced in commit.
e.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109062#c1
The gcc project itself has ~6k lines of python in the git commit
hooks and part of that handles "message" customization.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-03-10 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 16:44 GTI TAC Meeting Notes 2023-06-08 Carlos O'Donell
2023-03-08 19:29 ` Konstantin Ryabitsev
2023-03-10 4:50 ` Carlos O'Donell [this message]
2023-03-10 8:01 ` Martin Liška
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=83b7663a-114d-6fcd-6a62-ed3e79ba65bb@redhat.com \
--to=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.org \
--cc=jeffreyalaw@gmail.com \
--cc=konstantin@linuxfoundation.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).