From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] dlm: master - dlm_controld: remove ccs and new Makefile
Date: Fri, 30 Sep 2011 13:07:01 +0200 [thread overview]
Message-ID: <4E85A2D5.3080707@redhat.com> (raw)
In-Reply-To: <20110929220240.64C111200FE@lists.fedorahosted.org>
On 09/30/2011 12:02 AM, David Teigland wrote:
> add a normal, sane Makefile
If you plan to drop autoconf+autotool, that is your call (I disagree for
several reasons, but it's your project and I am not going to argue), but
you need to do it all over the tree, basically going back to something
similar in what's in STABLE31.
Placing a Makefile there, will be overridden by ./autogen.sh +
configure, that looks obvious to use since they are there in the top dir.
If you just need help to include those new options you need in
Makefile.am, I am more than happy to help you.
Fabio
next parent reply other threads:[~2011-09-30 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110929220240.64C111200FE@lists.fedorahosted.org>
2011-09-30 11:07 ` Fabio M. Di Nitto [this message]
2011-09-30 15:01 ` [Cluster-devel] dlm: master - dlm_controld: remove ccs and new Makefile David Teigland
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=4E85A2D5.3080707@redhat.com \
--to=fdinitto@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 NNTP newsgroup(s).