From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Simulators --with-pkgversion --with-bugurl support
Date: Sun, 08 Jun 2008 19:14:00 -0000 [thread overview]
Message-ID: <20080608151104.P91373@dair.pair.com> (raw)
In-Reply-To: <20080608143927.C38609@dair.pair.com>
On Sun, 8 Jun 2008, Hans-Peter Nilsson wrote:
> On Fri, 6 Jun 2008, Joseph S. Myers wrote:
> > +version.c: Makefile ../../gdb/version.in
>
> Could it be done some other way? For example with a placeholder
> sim/version.in automatically updated from (depending on)
> gdb/version.in? Or just having a separate sim/version.in?
Looking closer, the presence of the gdb subdir by itself doesn't
seem to be of significance or at all trig anything, as opposed
to gdb/configure, so maybe the most pragmatic solution is to add
gdb/version.in to the sim CVS module.
Would that be ok?
brgds, H-P
next prev parent reply other threads:[~2008-06-08 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 20:45 Joseph S. Myers
2008-06-07 1:15 ` Daniel Jacobowitz
2008-06-08 18:50 ` Hans-Peter Nilsson
2008-06-08 19:14 ` Hans-Peter Nilsson [this message]
2008-06-09 10:27 ` Joseph S. Myers
2008-06-09 12:06 ` Daniel Jacobowitz
2008-06-09 13:59 ` Hans-Peter Nilsson
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=20080608151104.P91373@dair.pair.com \
--to=hp@bitrange.com \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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