From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Trivial: Remove unused variable in c_printstr
Date: Wed, 04 Jul 2012 20:00:00 -0000 [thread overview]
Message-ID: <20120704195953.GA27907@host2.jankratochvil.net> (raw)
In-Reply-To: <20120704131022.5cf91770@spoyarek>
Hi Siddhesh,
On Wed, 04 Jul 2012 09:40:22 +0200, Siddhesh Poyarekar wrote:
> Ugh, sorry, I didn't remove the ChangeLog hunk from my diff. Here it is
> attached now. Also fixed typo in the ChangeLog.
[...]
> * c-lang.c (c_printstr): Remove unused variable WIDTH.
this patch is both pre-approved and also obvious, your work is also covered by
Red Hat FSF contract, could you file write-after-approval request?
http://sourceware.org/cgi-bin/pdw/ps_form.cgi
Thanks,
Jan
next prev parent reply other threads:[~2012-07-04 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 7:34 Siddhesh Poyarekar
2012-07-04 7:40 ` Siddhesh Poyarekar
2012-07-04 20:00 ` Jan Kratochvil [this message]
2012-07-05 1:03 ` Siddhesh Poyarekar
2012-07-06 5:48 ` Siddhesh Poyarekar
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=20120704195953.GA27907@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@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