public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: drow@sources.redhat.com To: gdb-prs@sources.redhat.com, mkl@pengutronix.de, nobody@sources.redhat.com, rsc@pengutronix.de Subject: Re: build/2176: CPPFLAGS and are not saved in Makefile Date: Tue, 28 Oct 2008 13:11:00 -0000 [thread overview] Message-ID: <20081028131150.31604.qmail@sourceware.org> (raw) Synopsis: CPPFLAGS and are not saved in Makefile State-Changed-From-To: open->closed State-Changed-By: drow State-Changed-When: Tue Oct 28 13:11:50 2008 State-Changed-Why: Now fixed in CVS. http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=2176
next reply other threads:[~2008-10-28 13:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-28 13:11 drow [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-11-14 15:36 drow 2006-09-25 10:18 mkl
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=20081028131150.31604.qmail@sourceware.org \ --to=drow@sources.redhat.com \ --cc=gdb-gnats@sources.redhat.com \ --cc=gdb-prs@sources.redhat.com \ --cc=mkl@pengutronix.de \ --cc=nobody@sources.redhat.com \ --cc=rsc@pengutronix.de \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).