kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Out of Date Project Ideas on Btrfs
Date: Thu, 9 Apr 2015 18:07:24 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1504091805110.13546@localhost> (raw)
In-Reply-To: <5526F630.6010706@gmail.com>

On Thu, 9 Apr 2015, nick wrote:

> Greetings All,

> I have been searching for work related to the btrfs file system. I
> am wondering if there is any that is still valid on the Project
> Ideas page of the wiki as most of it seems out of date to me. The
> only one that seems to be still valid is the Rename syscall new
> parameters needing to be supported by btrfs as most of the others
> including fs_info rather then root object to certain functions as
> parameters seem very out of date to me.

  why do you keep asking about btrfs ***here***? go talk to the btrfs
maintainers, fer gods sake. if you're utterly incapable of using
google, here, let me help:

  https://btrfs.wiki.kernel.org/index.php/Main_Page

rday

p.s. now do you understand the concept of "spoon feeding?" sheesh ...

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2015-04-09 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 21:59 Out of Date Project Ideas on Btrfs nick
2015-04-09 22:07 ` Robert P. J. Day [this message]
2015-04-09 22:08   ` nick

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=alpine.LFD.2.11.1504091805110.13546@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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;
as well as URLs for NNTP newsgroup(s).