Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: How are userspace & kernelspace kept in sync?
Date: Fri, 05 Apr 2013 17:48:56 -0500	[thread overview]
Message-ID: <515F54D8.4050903@redhat.com> (raw)

One thing led to another in poking around the code, and I realized
that while userspace has lots of code copied from the kernel, it
was last copied in 2008, in many cases.  ;)

What's the plan here, how are userspace & kernelspace to be kept
in sync?

New features fairly obviously hit both, but what about bugfixes
that hit one codebase or the other?

Is it clear (to anyone) which code needs to be synced?

Should it be done as a wholesale sync-up/rebase from time to
time, or should commits be merged from one to the other?

Just wondering,
Thanks,
-Eric

             reply	other threads:[~2013-04-05 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 22:48 Eric Sandeen [this message]
2013-04-06  0:20 ` How are userspace & kernelspace kept in sync? Josef Bacik
2013-04-06  0:34   ` Eric Sandeen

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=515F54D8.4050903@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-btrfs@vger.kernel.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