From: fabbione@sourceware.org <fabbione@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/daemon Makefile
Date: 22 Dec 2007 12:18:55 -0000 [thread overview]
Message-ID: <20071222121855.3784.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: fabbione at sourceware.org 2007-12-22 12:18:55
Modified files:
group/daemon : Makefile
Log message:
Convert to use make/clean.mk
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/Makefile.diff?cvsroot=cluster&r1=1.24&r2=1.25
--- cluster/group/daemon/Makefile 2007/12/21 20:13:53 1.24
+++ cluster/group/daemon/Makefile 2007/12/22 12:18:54 1.25
@@ -33,8 +33,7 @@
${TARGET}: ${OBJS}
$(CC) -o $@ $^ $(LDFLAGS)
-clean:
- rm -f *.o groupd
+clean: generalclean
install: all
install -d ${sbindir}
next reply other threads:[~2007-12-22 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 12:18 fabbione [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 19:55 [Cluster-devel] cluster/group/daemon Makefile teigland
2006-06-12 22:55 cfeist
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=20071222121855.3784.qmail@sourceware.org \
--to=fabbione@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 NNTP newsgroup(s).