Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH v2] sim: generate build dependencies on the fly
Date: Thu, 29 Sep 2011 02:14:00 -0000	[thread overview]
Message-ID: <201109282203.04338.vapier@gentoo.org> (raw)
In-Reply-To: <1310540262-31796-1-git-send-email-vapier@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 257 bytes --]

On Wednesday, July 13, 2011 02:57:42 Mike Frysinger wrote:
> Lift the code that GDB is using to generate dependencies on the fly and
> port it over to the sim.  Now people shouldn't have to manually maintain
> these in their Makefile's now.

ping ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-09-29  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  5:18 [PATCH] " Mike Frysinger
2011-07-13  8:26 ` [PATCH v2] " Mike Frysinger
2011-09-29  2:14   ` Mike Frysinger [this message]
2011-10-18 11:57     ` Mike Frysinger
2011-11-01 17:28       ` Mike Frysinger
2011-11-27 18:22         ` Mike Frysinger
2011-12-03 18:24 ` [PATCH] " Mike Frysinger

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=201109282203.04338.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=toolchain-devel@blackfin.uclinux.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