From: Nick Clifton <nickc@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: Obvious fix to remote-rdp.c ?
Date: Tue, 27 Mar 2001 09:11:00 -0000 [thread overview]
Message-ID: <p066gvi1cs.fsf@elmo.cygnus.com> (raw)
Hi Guys,
I think that the following patch ought to be covered under the
obvious fix rule, but since I am not a maintainer, I am seeking
approval before committing it.
Cheers
Nick
2001-03-27 Nick Clifton <nickc@redhat.com>
* remote-rdp.c (rdp_set_command_line): Add missing double quote.
Index: remote-rdp.c
===================================================================
RCS file: /cvs/src/src/gdb/remote-rdp.c,v
retrieving revision 1.14
diff -p -r1.14 remote-rdp.c
*** remote-rdp.c 2001/03/20 01:37:09 1.14
--- remote-rdp.c 2001/03/27 17:08:12
*************** rdp_set_command_line (char *command, cha
*** 699,705 ****
if (commandline != NULL)
xfree (commandline);
! xasprintf (&commandline, %s %s", command, args);
}
static void
--- 699,705 ----
if (commandline != NULL)
xfree (commandline);
! xasprintf (&commandline, "%s %s", command, args);
}
static void
next reply other threads:[~2001-03-27 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 9:11 Nick Clifton [this message]
2001-03-27 9:20 ` Fernando Nasser
2001-03-27 11:52 ` Michael Snyder
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=p066gvi1cs.fsf@elmo.cygnus.com \
--to=nickc@redhat.com \
--cc=gdb-patches@sources.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