From: Donald Douwsma <donaldd@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: current cvs doesn't compile
Date: Mon, 03 Dec 2007 10:23:26 +1100 [thread overview]
Message-ID: <47533E6E.1010508@sgi.com> (raw)
In-Reply-To: <20071130101824.GA4419@lst.de>
Christoph Hellwig wrote:
> On Fri, Nov 30, 2007 at 11:11:53AM +0100, Christoph Hellwig wrote:
>> xfs_mark_inode_dirty_sync is used in xfs_inode_item_format but isn't
>> actually declared anywhere.
>
> Sorry, this was due to me having some old patch applied still.
>
>> Btw, we also still have the bug that fs/xfs/Kbuild exists as an empty
>> files and without removing it nothing is recompiled at all.
>
> But this is still a real issue..
Hi Christoph,
http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/xfs/
Doesn't snow fs/xfs/Kbuild (except in the archives). I also did a fresh
cvs checkout of linux-2.6-xfs and its not there ether. Seems like this
is only happening when updating an existing workarea.
There could be a stale entry in fs/xfs/CVS/Entries that is not
being removed by an update/checkout. Could you send us your Entries
file so we can figure out whats happening?
Don
prev parent reply other threads:[~2007-12-02 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 10:11 current cvs doesn't compile Christoph Hellwig
2007-11-30 10:18 ` Christoph Hellwig
2007-12-02 23:23 ` Donald Douwsma [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=47533E6E.1010508@sgi.com \
--to=donaldd@sgi.com \
--cc=hch@lst.de \
--cc=xfs@oss.sgi.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