From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] remove pointless call.
Date: Mon, 12 May 2003 19:24:00 -0000 [thread overview]
Message-ID: <3EBFF3A8.3080306@redhat.com> (raw)
In-Reply-To: <16d001c318ba$7eaa0080$0202040a@catdog>
>> > Okay to apply? The TARGET_FIND_AND_OPEN_SOLIB removes the need for this
>> > call.
>
>>
>> Yes (obvious?).
>
>
> Is it in general okay to just post and apply patches to my own files if
> they're obvious?
Yes. Whats the worst you could do, break it? :-)
> Do I need to be put down as a target specific maintainer
> or some such?
I'll go and ask the global maintainers.
Andrew
prev parent reply other threads:[~2003-05-12 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 18:19 Kris Warkentin
2003-05-12 18:57 ` Andrew Cagney
2003-05-12 19:16 ` Kris Warkentin
2003-05-12 19:24 ` Andrew Cagney [this message]
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=3EBFF3A8.3080306@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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