linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Cc: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsdocs: master branch updated to 242d533
Date: Thu, 8 Sep 2016 13:40:31 +1000	[thread overview]
Message-ID: <20160908034031.GU30056@dastard> (raw)

[-- Attachment #1: Type: text/plain, Size: 2523 bytes --]

Hi folks,

The xfs documentation repository at

git://git.kernel.org/pub/scm/fs/xfs/xfs-documentation.git

has just been updated.

The new head of the master branch is commit:

242d533 xfsdocs: document the realtime reverse mapping btree

New Commits:

Darrick J. Wong (7):
      [8b5acc6] journaling_log: fix some typos in the section about EFDs
      [3db09b6] xfsdocs: document known testing procedures
      [afcda10] xfsdocs: update the on-disk format with changes for Linux 4.5
      [6e7cbb4] xfsdocs: move the discussions of short and long format btrees to a separate chapter
      [4302a13] xfsdocs: reverse-mapping btree documentation
      [5a9c232] xfsdocs: document refcount btree and reflink
      [242d533] xfsdocs: document the realtime reverse mapping btree


Code Diffstat:

 .../allocation_groups.asciidoc                       | 119 ++++----
 design/XFS_Filesystem_Structure/btrees.asciidoc      | 196 +++++++++++++
 .../XFS_Filesystem_Structure/data_extents.asciidoc   |  72 +----
 design/XFS_Filesystem_Structure/directories.asciidoc |   1 +
 design/XFS_Filesystem_Structure/docinfo.xml          |  47 ++++
 .../internal_inodes.asciidoc                         |   2 +
 .../XFS_Filesystem_Structure/journaling_log.asciidoc | 320 +++++++++++++++++++++-
 design/XFS_Filesystem_Structure/magic.asciidoc       |   9 +
 .../XFS_Filesystem_Structure/ondisk_inode.asciidoc   |  50 +++-
 .../XFS_Filesystem_Structure/reconstruction.asciidoc |  53 ++++
 design/XFS_Filesystem_Structure/refcountbt.asciidoc  | 145 ++++++++++
 design/XFS_Filesystem_Structure/reflink.asciidoc     |  40 +++
 design/XFS_Filesystem_Structure/rmapbt.asciidoc      | 307 +++++++++++++++++++++
 design/XFS_Filesystem_Structure/rtrmapbt.asciidoc    | 234 ++++++++++++++++
 design/XFS_Filesystem_Structure/testing.asciidoc     |  23 ++
 .../xfs_filesystem_structure.asciidoc                |  12 +
 16 files changed, 1482 insertions(+), 148 deletions(-)
 create mode 100644 design/XFS_Filesystem_Structure/btrees.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/reconstruction.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/refcountbt.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/reflink.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/rmapbt.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/rtrmapbt.asciidoc
 create mode 100644 design/XFS_Filesystem_Structure/testing.asciidoc
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-09-08  3:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160908034031.GU30056@dastard \
    --to=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).