From: Andrew Cagney <ac131313@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] target_read_aux_vector
Date: Wed, 08 Oct 2003 14:11:00 -0000 [thread overview]
Message-ID: <3F841B0F.1060104@redhat.com> (raw)
In-Reply-To: <200310070208.h9728fCd011811@magilla.sf.frob.com>
> Roland, not sure why you posted this. The relevant discussion has still
>> not been resolved.
>
>
> I like to write code more than I like to speculate about how I will write
> it. My favorite sort of discussion about code includes exchanges of "like
> this? [and some code that might work]", "no, different because of foo and
> bar", "ok, so like this? [and some different code that might work]", and so
> on. Let's have a discussion like that!
>
> I developed one of the alternatives being discussed to flesh out the issues
> with doing it that way. In the process, I noticed that part of it was
> independently useful (fixing a missing part of gcore functionality). I
> posted this patch to demonstrate the utility of this alternative for the
> purpose we are discussing, and the bonus feature that my patch as posted
> fixes an existing, separate shortcoming of gdb. Now discuss!
In that case, can I suggest posting such things as [wip]
(work-in-progress). That way it's clear that the change is intended as
a discussion point, and not a final waiting-on-approval patch. It
unfortunatly comes across as very strange when someone posts what looks
like the final [rfa] for for a specific variant of a change when the
related technical discussion has not been resolved.
enjoy,
Andrew
next prev parent reply other threads:[~2003-10-08 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 1:48 Roland McGrath
2003-10-07 1:53 ` Daniel Jacobowitz
2003-10-07 1:58 ` Andrew Cagney
2003-10-07 2:08 ` Daniel Jacobowitz
2003-10-07 2:08 ` Roland McGrath
2003-10-08 14:11 ` Andrew Cagney [this message]
2003-10-08 19:10 ` Jim Blandy
2003-10-08 20:10 ` Andrew Cagney
2003-10-09 0:51 ` Michael Snyder
2003-10-09 0:55 ` Roland McGrath
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=3F841B0F.1060104@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@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