h1. Repository and Branches

I've created a new git repository

(/pub/scm/linux/kernel/git/ericvh/v9fs.git) to eventually replace v9fs-devel.git. This tree will be organized a bit differently with most stuff stored in the following branches:

* master: linus: will have a pristine linus tree.

* mm: will have the most recent andrew morton release.

* v9fs-devel: old-v9fs: will be (at least temporarily) hold the old v9fs-devel tree.

* test: will contain my development tree (which gets pulled into mm) current test branch (unstable)

* standalone-test: will contain a version of test with ifdefs to help compile on older kernels.

* release: will contain changes which have passed our regression suite.

* for-linus: standalone: will contain a version of release with ifdefs to help compile on older kernels.

The fs/9p directory of the standalone trees will be patches snapshotted in sf.net CVS under linux-9p on a somewhat regular basis for linus folks that want to only build the module.

Most folks will probably only want to pull during merge windows deal with the release branch or grabbing the standalone branch from CVS.

h1. Regression Testing

Right now we request folks perform a sanity check on any changes by running the following benchmarks (available from v9fs CVS on sf.net under the test module):

mount -t 9P 127.0.0.1 /mnt/9

cd /mnt/9/var/tmp

fsx -N 100 -W -d testfile

Bonnie -s 1

echo run | postmark

ls -l

cd /

umount /mnt/9

A more complicated regression suite is being developed and it will be distributed (along with scripts which run it) shortly. We also request that folks run their builds with Sparse (C=1) to make sure the build is _really_ clean.

h1. Patch Acceptance/Test Process

Please generate patch files with git (git-format-patch-script) and inline email them to v9fs-developer. These patches will go in my patch queue and eventually be merged first into the test branch for baseline regression. Patches passing baseline regression will be merged into the release branch for more thorough testing by the v9fs community, and then be sent as patches to LKML.

h1. Code Style

Follow the Linux kernel guidelines found in Documentation/CodingStyle.

h1. Repository and Branches

I've created a new git repository

(/pub/scm/linux/kernel/git/ericvh/v9fs.git) to eventually replace v9fs-devel.git. This tree will be organized a bit differently with most stuff stored in the following branches:

* linus: will have a pristine linus tree.

* mm: will have the most recent andrew morton release.

* old-v9fs: will (at least temporarily) hold the old v9fs-devel tree.

* test: will contain my current test branch (unstable)

* standalone-test: will contain a version of test with ifdefs to help compile on older kernels.

* release: will contain changes which have passed our regression suite.

* standalone: will contain a version of release with ifdefs to help compile on older kernels.

The fs/9p directory of the standalone trees will be snapshotted in sf.net CVS under linux-9p on a somewhat regular basis for folks that want to only build the module.

Most folks will probably only want to deal with the release branch or grabbing the standalone branch from CVS.

h1. Regression Testing

Right now we request folks perform a sanity check on any changes by running the following benchmarks (available from v9fs CVS on sf.net under the test module):

mount -t 9P 127.0.0.1 /mnt/9

cd /mnt/9/var/tmp

fsx /root/fsx/fsx -N 100 -W -d testfile

Bonnie /root/bonnie/bonnie -s 1

echo run | postmark /root/postmark/postmark

ls -l

cd /

umount /mnt/9

A more complicated regression suite is being developed and it will be distributed (along with scripts which run it) shortly. We also request that folks run their builds with Sparse (C=1) to make sure the build is _really_ clean.

h1. Patch Acceptance/Test Process

Please generate patch files with git (git-format-patch-script) and inline email them to v9fs-developer. These patches will go in my patch queue and eventually be merged first into the test branch for baseline regression. Patches passing baseline regression will be merged into the release branch for more thorough testing by the v9fs community, and then be sent as patches to LKML.

h1. Code Style

Follow the Linux kernel guidelines found in Documentation/CodingStyle.

h1. Repository and Branches

I've created a new git repository

(/pub/scm/linux/kernel/git/ericvh/v9fs.git) to eventually replace v9fs-devel.git. This tree will be organized a bit differently with most stuff stored in the following branches:

* linus: will have a pristine linus tree.

* mm: will have the most recent andrew morton release.

* old-v9fs: will (at least temporarily) hold the old v9fs-devel tree.

* test: will contain my current test branch (unstable)

* standalone-test: will contain a version of test with ifdefs to help compile on older kernels.

* release: will contain changes which have passed our regression suite.

* standalone: will contain a version of release with ifdefs to help compile on older kernels.

The fs/9p directory of the standalone trees will be snapshotted in sf.net CVS under linux-9p on a somewhat regular basis for folks that want to only build the module.

Most folks will probably only want to deal with the release branch or grabbing the standalone branch from CVS.

h1. Regression Testing

Right now we request folks perform a sanity check on any changes by running the following benchmarks (available from v9fs CVS on sf.net under the test module):

bq. mount -t 9P 127.0.0.1 /mnt/9

bq. cd /mnt/9/var/tmp

/root/fsx/fsx -N 100 -W -d testfile

/root/bonnie/bonnie -s 1

echo run | /root/postmark/postmark

ls -l

cd /

umount /mnt/9

bq.

h1. Patch Acceptance/Test Process

h1. Code Style

h1. Repository and Branches

I've created a new git repository

(/pub/scm/linux/kernel/git/ericvh/v9fs.git) to eventually replace v9fs-devel.git. This tree will be organized a bit differently with most stuff stored in the following branches:

* linus: will have a pristine linus tree.

* mm: will have the most recent andrew morton release.

* old-v9fs: will (at least temporarily) hold the old v9fs-devel tree.

* test: will contain my current test branch (unstable)

* standalone-test: will contain a version of test with ifdefs to help compile on older kernels.

* release: will contain changes which have passed our regression suite.

* standalone: will contain a version of release with ifdefs to help compile on older kernels.

The fs/9p directory of the standalone trees will be snapshotted in sf.net CVS under linux-9p on a somewhat regular basis for folks that want to only build the module.

Most folks will probably only want to deal with the release branch or grabbing the standalone branch from CVS.

h1. Regression Testing

Right now we request folks perform a sanity check on any changes by running the following benchmarks (available from v9fs CVS on sf.net under the test module):

bq.

mount -t 9P 127.0.0.1 /mnt/9

bq. cd /mnt/9/var/tmp

/root/fsx/fsx -N 100 -W -d testfile

/root/bonnie/bonnie -s 1

echo run | /root/postmark/postmark

ls -l

cd /

umount /mnt/9

bq.

h1. Patch Acceptance/Test Process

h1. Code Style