Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Fix various problems with "printf" and warnings
Date: Sun, 22 Jan 2006 06:38:00 -0000	[thread overview]
Message-ID: <8f2776cb0601212238g7e3c6c8cn30c73bfc4d7b3d3c@mail.gmail.com> (raw)
In-Reply-To: <20060122003117.GC8088@nevyn.them.org>

Awesome.  That doesn't look like a terribly entertaining bit of work.  :)

Should we be using sed s/...//g?

I guess this patch shouldn't address such issues, but those Makefile
variable names are pretty wild.  The 'CFLAGS' lexeme sometimes appears
in the middle, sometimes at the end; we use 'INTERNAL' and 'GDB' to
mean essentially the same thing; and it seems sometimes we just drop
that altogether.


  parent reply	other threads:[~2006-01-22  6:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22  0:31 Daniel Jacobowitz
2006-01-22  1:22 ` Andreas Schwab
2006-01-22  2:36   ` Daniel Jacobowitz
2006-01-22  4:28 ` Eli Zaretskii
2006-01-22  4:56   ` Daniel Jacobowitz
2006-01-22 19:10     ` Eli Zaretskii
2006-01-22  6:38 ` Jim Blandy [this message]
2006-01-22 16:36   ` Daniel Jacobowitz
2006-02-02  2:26 ` Daniel Jacobowitz

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=8f2776cb0601212238g7e3c6c8cn30c73bfc4d7b3d3c@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sourceware.org \
    /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