From: Lachlan McIlroy <lachlan@sgi.com>
To: lachlan@sgi.com
Cc: David Chinner <dgc@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: oss git tree busted....
Date: Thu, 17 Apr 2008 17:13:18 +1000 [thread overview]
Message-ID: <4806F88E.3060809@sgi.com> (raw)
In-Reply-To: <4806EFF8.4000908@sgi.com>
The master branch should now be fully up-to-date. The three mods listed
below were in the merge.
Lachlan McIlroy wrote:
> I pushed all available changes, at the time I did the merge, into the
> master
> branch so all these changes must have been checked in after (or during) the
> last merge. I'll run another merge now.
>
> David Chinner wrote:
>> Lachlan,
>>
>> Looks like the last update fom the ptools tree missed a bunch of mods.
>>
>> This (log of all changes with fs/xfs):
>>
>> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=history;f=fs/xfs;hb=HEAD
>>
>>
>> Shows:
>>
>> 6 days ago Eric Sandeen [XFS] Ensure "both" features2 slots are
>> consistent
>> 6 days ago David Chinner [XFS] Fix superblock features2 field
>> alignment problem
>> 6 days ago Eric Sandeen [XFS] remove shouting-indirection macros
>> from xfs_sb.h
>> 7 days ago David Chinner [XFS] Catch log unmount failures.
>> 7 days ago David Chinner [XFS] Sanitise xfs_log_force error checking.
>> 7 days ago David Chinner [XFS] Check for errors when changing
>> buffer pointers.
>> 7 days ago David Chinner [XFS] Don't allow silent errors in
>> xfs_inactive().
>> 7 days ago David Chinner [XFS] Catch errors from xfs_imap().
>> 7 days ago David Chinner [XFS] xaiki@sgi.com
>> xfs_bulkstat_one_dinode() never ...
>> 7 days ago David Chinner [XFS] xfs_iflush_fork() never returns an
>> error.
>> 7 days ago David Chinner [XFS] Catch unwritten extent conversion
>> errors.
>> 7 days ago David Chinner [XFS] xfs_bdwrite() does not return errors.
>> ....
>>
>> It appears that most of the error checking changes I made have been
>> pushed. Note that there's an error in one fo the titles that the
>> scripts have not caught (the reviewers email address!). Can you fix
>> this commit up?
>>
>> However the real problem is that there are several mods that have
>> not been pushed:
>>
>> xfs-linux-melb:xfs-kern:30836a
>> xfs-linux-melb:xfs-kern:30838a
>> xfs-linux-melb:xfs-kern:30845a
>>
>> These are fixes to my original series, and without them you
>> cannot mount an XFS filesystem at all. Can you please push these
>> to the git tree ASAP?
>>
>> Cheers,
>>
>> Dave.
>
>
>
next prev parent reply other threads:[~2008-04-17 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 3:51 oss git tree busted David Chinner
2008-04-17 6:36 ` Lachlan McIlroy
2008-04-17 7:13 ` Lachlan McIlroy [this message]
2008-04-17 9:00 ` David Chinner
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=4806F88E.3060809@sgi.com \
--to=lachlan@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--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