From: Dave Chinner <david@fromorbit.com>
To: sam supramani <suprasam@crossmeta.org>
Cc: xfs@oss.sgi.com
Subject: Re: Identify patches for superblock changes for Crossmeta
Date: Wed, 1 Feb 2012 09:24:13 +1100 [thread overview]
Message-ID: <20120131222413.GO9090@dastard> (raw)
In-Reply-To: <CAM=3LEd2yu6rgSCg=6-Mop7wgKK5FnVKx6E=H2NapzJQ9ahSeg@mail.gmail.com>
On Tue, Jan 31, 2012 at 09:13:36AM -0800, sam supramani wrote:
> Hi,
>
> I am trying to get Crossmeta that includes windows port of XFS file
> system,
> to recognize newer ondisk format changes seen with the newer
> linux kernels.(RHEL6)
> The crossmeta-xfs port in https://github.com/crossmeta/sgi is quite
> old based on XFS 1.1 release with log v2 patches added later.
>
> I am interested in knowing submittal ID for the following changes;
> attr=2 lazy-count=1.
You've got a 10+ year old code base. That's a significant problem -
nobody is going to search 10 years worth of history for you. It's
all in various git trees around the place, so you should probably
learn to use git blame....
BTW, filesystems that have been mounted on windows are completely
unsupportable by the Linux community, so using crossmeta to access
your Linux XFS filesystem is not an advisable thing to do in the
first place...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-01-31 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 17:13 Identify patches for superblock changes for Crossmeta sam supramani
2012-01-31 22:24 ` Dave Chinner [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=20120131222413.GO9090@dastard \
--to=david@fromorbit.com \
--cc=suprasam@crossmeta.org \
--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