From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: suggestion for future changes to GDB website
Date: Sat, 29 Oct 2005 10:32:00 -0000 [thread overview]
Message-ID: <uacgssl4j.fsf@gnu.org> (raw)
In-Reply-To: <20051028181043.GA31049@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 28 Oct 2005 14:10:43 -0400)
> Date: Fri, 28 Oct 2005 14:10:43 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
>
> On Fri, Oct 28, 2005 at 11:03:25AM -0700, Joel Brobecker wrote:
> > All the developers who answered were in favor of posting the changes
> > one way or the other. Let's agree on one of the following forms:
> >
> > 1. Post patch to gdb-patches BEFORE checkin
> > Not sure how to make things work: Approval needed? Etc.
> >
> > 2. Post patch to gdb-patches AFTER checkin
> >
> > 3. Have an automated system that sends the patch with RH to
> > a mailing-list. Could be a dedicated mailing-list, or one
> > of the GDB existing mailing lists.
> >
> > I'm OK with either of the proposals.
>
> How about just treating it like part of GDB? Allow global maintainers
> to make or approve changes, and list it in MAINTAINERS.
Yep, that's what I'd suggest as well. Wed already have procedures in
place for dealing with RFA's, so let's just use them.
next prev parent reply other threads:[~2005-10-29 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 0:29 Joel Brobecker
[not found] ` <vt2fyqpw2es.fsf@theseus.home.>
2005-10-26 6:45 ` Joel Brobecker
2005-10-26 19:36 ` Daniel Jacobowitz
[not found] ` <vt2ek67vlew.fsf@theseus.home.>
2005-10-28 18:10 ` Joel Brobecker
2005-10-28 18:16 ` Daniel Jacobowitz
2005-10-28 18:20 ` Joel Brobecker
2005-10-29 10:32 ` Eli Zaretskii [this message]
2005-10-26 12:55 ` Eli Zaretskii
2005-10-26 12:57 ` Daniel Jacobowitz
2005-10-26 22:29 ` Eli Zaretskii
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=uacgssl4j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/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