From: Sergio Durigan Junior <sergiodj@redhat.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Simon Marchi <simark@simark.ca>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4] GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested.
Date: Mon, 29 Oct 2018 16:42:00 -0000 [thread overview]
Message-ID: <87a7mwd7r0.fsf@redhat.com> (raw)
In-Reply-To: <20181029162513.oztznqp74gudrqgm@jocasta.intra> (John Darrington's message of "Mon, 29 Oct 2018 17:25:14 +0100")
On Monday, October 29 2018, John Darrington wrote:
> On Mon, Oct 29, 2018 at 03:51:55PM +0000, Simon Marchi wrote:
> On 2018-10-29 5:11 a.m., Rainer Orth wrote:
> > Hi John,
> >
> >> However I've checked in a fix for this issue, and tested it by building
> >> natively with a hacked set of standard include headers.
> >
> > you always need to post patches here, if only for reference.
>
> Doesn't that make the gdb-cvs list completely redundant?
>
> Not only should you post here the patches you push as obvious, but I don't
> think that this:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=98a17ece013cb94cd602496b9efb92b8816b3953
>
> falls under the obvious rule:
>
> But a number of people had complained that their build was broken, and
> this was a fix for that. I judged that in consideration of those
> people fixding their problem was more important than strict observance
> of protocol.
>
> I can't judge whether the patch is right or not with a quick glance, but it
> certainly is complex enough to warrant a discussion (as Rainer's reply below
> shows).
>
>
> Additionally, it seems like the initial 4-patch series was pushed without
> explicit approval from a maintainer (at least I can't find any). Next time,
> please wait to have an approval before pushing. If you are not sure whether
> a reply constitutes an a approval, it's better to ask the maintainer to
> clarify.
>
> All of those patches were certainly discussed. In the past, when I've
> followed up a person who has commented on a patch, but been vague about
> approval, I have had either a piqued response; or no response at all.
We were certainly discussing the patches, but they were not approved by
anyone. It's also worth mentioning that I raised various points that
were not addressed (even though we discussed them). It is still a
requirement that the patches need to be approved by at least one
maintainer before it is pushed to the repository.
> If you think it necesary however I can revert anything you think hasn't
> had enough discussion.
Yes, please. The patch series is not ready to be pushed yet; there are
a bunch of points I raised that were not addressed (and are now causing
the failures). I am not a global maintainer, but it is my opinion that
the patch series should be reverted for now. We can continue discussing
and fixing things with it here in the list.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-10-29 16:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 17:33 Gdbserver can listen on local domain sockets John Darrington
2018-10-09 17:33 ` [PATCH] GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested John Darrington
2018-10-09 17:56 ` Eli Zaretskii
2018-10-09 18:02 ` Pedro Alves
2018-10-09 18:41 ` John Darrington
2018-10-09 18:53 ` Pedro Alves
2018-10-09 19:00 ` John Darrington
2018-10-09 19:06 ` Pedro Alves
2018-10-13 17:58 ` [PATCH 1/4] " John Darrington
2018-10-13 17:58 ` [PATCH 2/4] GDB: Document the unix::/path/to/socket of remote connection John Darrington
2018-10-13 18:11 ` Eli Zaretskii
2018-10-15 9:31 ` Simon Tatham
2018-10-18 20:21 ` Sergio Durigan Junior
2018-10-13 17:58 ` [PATCH 4/4] GDB: Remote target can now accept the form unix::/path/to/socket John Darrington
2018-10-13 17:58 ` [PATCH 3/4] GDB: Fix documentation for invoking GDBSERVER John Darrington
2018-10-13 18:10 ` Eli Zaretskii
2018-10-18 20:27 ` Sergio Durigan Junior
2018-10-19 7:05 ` John Darrington
2018-10-19 20:45 ` Sergio Durigan Junior
2018-10-21 7:33 ` John Darrington
2018-10-21 16:47 ` Sergio Durigan Junior
2018-10-23 18:25 ` John Darrington
2018-10-23 18:58 ` Sergio Durigan Junior
2018-10-13 18:12 ` [PATCH 1/4] GDBSERVER: Listen on a unix domain (instead of TCP) socket if requested Eli Zaretskii
2018-10-18 20:18 ` Sergio Durigan Junior
2018-10-19 18:55 ` John Darrington
2018-10-19 19:43 ` Sergio Durigan Junior
2018-10-28 16:20 ` Simon Marchi
2018-10-28 18:10 ` John Darrington
2018-10-28 18:51 ` Simon Marchi
2018-10-29 8:24 ` John Darrington
2018-10-29 9:13 ` Rainer Orth
2018-10-29 9:38 ` Rainer Orth
[not found] ` <4da7206f-6e6a-7aad-634e-a4485d99e988@ericsson.com>
[not found] ` <20181029162513.oztznqp74gudrqgm@jocasta.intra>
2018-10-29 16:42 ` Sergio Durigan Junior [this message]
2018-10-29 17:34 ` John Darrington
2018-10-31 13:54 ` Simon Marchi
2018-10-29 18:32 ` Simon Marchi
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=87a7mwd7r0.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=john@darrington.wattle.id.au \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=simark@simark.ca \
--cc=simon.marchi@ericsson.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