andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
bda2feeaf2
glusterfs/doc
History
Anoop C S bda2feeaf2 doc: Update release notes for Samba integration 
Change-Id: I2a246111522bd3cb0c9b228ed3387e72b0ac20a4
updates: bz#1672818
Signed-off-by: Anoop C S <anoopcs@redhat.com>
2019-03-12 20:56:57 +00:00
..
debugging Revert "iobuf: Get rid of pre allocated iobuf_pool and use per thread mem pool" 2019-01-08 11:16:03 +00:00
developer-guide Revert "iobuf: Get rid of pre allocated iobuf_pool and use per thread mem pool" 2019-01-08 11:16:03 +00:00
features posix: APIs in posix to get and set time attributes 2018-05-06 01:32:30 +00:00
release-notes doc: Update release notes for Samba integration 2019-03-12 20:56:57 +00:00
gluster.8 geo-rep: add no-verify and ssh-port options for create command 2018-11-26 05:04:46 +00:00
glusterd.8 doc: fix wrong description of localtime-logging in manpages 2019-01-11 07:41:50 +00:00
glusterfs.8 mount/fuse: expose auto-invalidation as a mount option 2019-02-02 03:07:35 +00:00
glusterfsd.8 mount/fuse: expose auto-invalidation as a mount option 2019-02-02 03:07:35 +00:00
Makefile.am build: add --without-server option 2018-02-19 17:38:55 +00:00
mount.glusterfs.8 fuse: reflect the actual default for lru-limit option 2019-02-25 15:26:08 +00:00
README.md doc: add coding-standard and commit-msg link in README 2018-09-11 22:55:23 +00:00

README.md

Developer Guide

Gluster's contributors can check about the internals by visiting Developer Guide Section. While it is not 'comprehensive', it can help you to get started.

Also while coding, keep Coding Standard in mind.

When you are ready to commit the changes, make sure you meet our Commit message standard.

Admin Guide

The gluster administration guide is maintained at github. The browsable admin guide can be found here.

The doc patch has to be sent against the above mentioned repository.

Features/Spec

The Gluster features which are 'in progress' or implemented can be found at github.

Upgrade Guide

The gluster upgrade guide is maintained at github. The browsable upgrade guide can be found here

The doc patch has to be sent against the above mentioned repository.

For more details about the docuemntation workflow please refer this discussion