From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb@sourceware.org
Subject: Re: using automake to generate Makefile.in
Date: Fri, 08 Jan 2016 19:11:00 -0000 [thread overview]
Message-ID: <20160108191103.GA20883@host1.jankratochvil.net> (raw)
In-Reply-To: <20160107214249.GF25548@vapier.lan>
On Thu, 07 Jan 2016 22:42:49 +0100, Mike Frysinger wrote:
> is there a reason we don't use automake in the tree to manage
> Makefile.in ?
IIRC Tom Tromey (also a coauthor of automake) wanted to do that or at least he
said it would be good to do that but just nobody has never done so.
Jan
next prev parent reply other threads:[~2016-01-08 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 21:42 Mike Frysinger
2016-01-08 19:11 ` Jan Kratochvil [this message]
2016-01-08 19:53 ` Mike Frysinger
2016-01-08 21:03 ` 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=20160108191103.GA20883@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).