From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
Mark Wielaard <mark@klomp.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
gdb@sourceware.org, "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>,
Pedro Alves <pedro@palves.net>
Subject: Re: setting up sim project web space
Date: Mon, 16 Jan 2023 07:17:39 +0400 [thread overview]
Message-ID: <Y8TB09eq5Nvl6LGN@adacore.com> (raw)
In-Reply-To: <Y8R3acn32lfPlXVK@vapier>
> > We can do a quick announcement on gdb-patches@, to let people
> > know, but other than that, it's a pretty limited audience for
> > this repository. Perhaps it'll encourage people to participate
> > in improving it.
>
> on that note, what is the policy for merging changes ? akin to other
> projects where there's maintainers & write-after-approval ? i can
> write up a quick MAINTAINERS doc for the repo.
I don't think there is a process. For my changes, the vast majority
have been about the release, which are routine changes, so I've just
pushed them and that's it.
For changes that can affect the contents more, we go through
gdb-patches, or at the very least I let people know by sending
the patch to gdb-patches.
That's about it so far.
--
Joel
next prev parent reply other threads:[~2023-01-16 3:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YZeHYvzZd+NTp+yy@vapier>
[not found] ` <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net>
[not found] ` <YZpQsaSI9EyvwoLs@adacore.com>
[not found] ` <ca4fd206bd854a3613bd54a7af4c4ad6534534b2.camel@klomp.org>
[not found] ` <YZ4e/i9H0BELlV0r@vapier>
[not found] ` <Y1a6/JlhRSgfVEx2@vapier>
[not found] ` <Y1ckAXF+qMU2qM7J@elastic.org>
[not found] ` <f0ce6ccc94b6255f7eaec29d39001a9a2a7f0968.camel@klomp.org>
[not found] ` <Y7U2SBTabZ1AjFo2@vapier>
[not found] ` <20230105223840.GI8237@gnu.wildebeest.org>
2023-01-05 22:43 ` Mark Wielaard
2023-01-06 6:22 ` Joel Brobecker
2023-01-10 18:27 ` Frank Ch. Eigler
2023-01-10 20:18 ` Mark Wielaard
2023-01-11 5:36 ` Joel Brobecker
2023-01-11 23:56 ` Mark Wielaard
2023-01-12 5:12 ` broken current onlinedocs Mike Frysinger
2023-01-12 7:30 ` Mark Wielaard
2023-01-16 3:42 ` Joel Brobecker
2023-01-15 22:00 ` setting up sim project web space Mike Frysinger
2023-01-16 3:17 ` Joel Brobecker [this message]
2021-11-17 17:27 Mike Frysinger
2021-11-17 18:46 ` Mark Wielaard
2021-11-18 0:19 ` Mike Frysinger
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=Y8TB09eq5Nvl6LGN@adacore.com \
--to=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=vapier@gentoo.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).