From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] UPDATED: building e2fsprogs-interim
Date: Fri, 15 Feb 2008 23:25:42 -0500 [thread overview]
Message-ID: <20080216042542.GD26734@mit.edu> (raw)
In-Reply-To: <47B5E188.6080502@redhat.com>
On Fri, Feb 15, 2008 at 01:01:28PM -0600, Eric Sandeen wrote:
> An update; running through the whole fedora build turned up another
> one (csum.o). Out of curiosity do things like ext2_fs.h (which are not
> generated) really need to be listed as dependencies?
Well, in an RPM build you probably don't need them, no.
But they are useful in an developer tree because if ext2_fs.h gets
modified, it's good to recompile all source files that include it ---
just to make sure any errors in the header file get caught.
- Ted
prev parent reply other threads:[~2008-02-16 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 18:26 [PATCH] building e2fsprogs-interim Eric Sandeen
2008-02-14 22:47 ` Andreas Dilger
2008-02-15 19:01 ` [PATCH] UPDATED: " Eric Sandeen
2008-02-16 4:25 ` Theodore Tso [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=20080216042542.GD26734@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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