From: Mike Frysinger <vapier@gentoo.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org, tromey@redhat.com
Subject: Re: using automake to generate Makefile.in
Date: Fri, 08 Jan 2016 19:53:00 -0000 [thread overview]
Message-ID: <20160108195318.GN25548@vapier.lan> (raw)
In-Reply-To: <20160108191103.GA20883@host1.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On 08 Jan 2016 20:11, Jan Kratochvil wrote:
> 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.
do we have a requirement that it be done treewide ?
or would people be fine with me doing (starting) in sim/ ?
doing it in just sim/ would allow for some limited testing
w/out breaking lots of people ...
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-08 19:53 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
2016-01-08 19:53 ` Mike Frysinger [this message]
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=20160108195318.GN25548@vapier.lan \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).