From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] avoid build failure: css.h: no such file
Date: Sun, 21 Jun 2009 10:02:11 +0200 [thread overview]
Message-ID: <87prcyqakc.fsf@meyering.net> (raw)
In-Reply-To: <1245501224.3665.335.camel@cerberus.int.fabbione.net> (Fabio M. Di Nitto's message of "Sat, 20 Jun 2009 14:33:44 +0200")
Fabio M. Di Nitto wrote:
> good to in of course :)
Pushed.
...
>> >From b124cd70ce01d12eb0a11e89c7f8c740cf4dbf30 Mon Sep 17 00:00:00 2001
>> From: Fabio M. Di Nitto <fdinitto@redhat.com>
>> Date: Fri, 19 Jun 2009 19:52:44 +0200
>> Subject: [PATCH] avoid build failure: css.h: no such file
>>
>> * fence/libfence/Makefile.am (libfence_la_CFLAGS): Fix typo:
>> s/css_CFLAGS/ccs_CFLAGS/
...
prev parent reply other threads:[~2009-06-21 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 17:53 [Cluster-devel] [PATCH] avoid build failure: css.h: no such file Jim Meyering
2009-06-19 21:42 ` Jim Meyering
2009-06-20 12:33 ` Fabio M. Di Nitto
2009-06-21 8:02 ` Jim Meyering [this message]
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=87prcyqakc.fsf@meyering.net \
--to=jim@meyering.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.