development/fossil: Updated for version 2.14.

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>

1 files changed, 32 insertions, 32 deletions

diff --git a/development/fossil/README b/development/fossil/README
index cb302ac679..af0f5691e7 100644
--- a/development/fossil/README
+++ b/development/fossil/README
@@ -3,33 +3,33 @@ created by D. Richard Hipp, the primary author of SQLite.
 
 Features:
 
-- tamper-proof artifact record
-- simple command-line interface
-- customizable web interface with JSON, RSS, CGI, wiki, and forum
-- online project documentation with full-text search capability
-- integrated PIC-like markup language for creating diagrams
-- online activity and ticket reports
-- user accounts with access controls
-- coherent versioning across all files
-- straightforward branching and merging
-- bisect searches to pinpoint behavior changes
+- Tamper-proof artifact record
+- Simple command-line interface
+- Customizable web interface with JSON, RSS, CGI, wiki, chat, and forum
+- Online project documentation with full-text search capability
+- Integrated PIC-like markup language for creating diagrams
+- Online activity and ticket reports
+- User accounts with access controls
+- Coherent versioning across all files
+- Straightforward branching and merging
+- Bisect searches to pinpoint behavior changes
 - SHA3-256 and hardened SHA1 checksums
 - FUSE filesystem makes all historical and branch revisions available
-- synchronization via http, https, ssh, and local/network filesystems
-- automated replication and backup
-- git import/export and Subversion/CVS import
-- nested checkouts to share common subtrees across related projects
-- checkout directory not cluttered with administrative files
-- support for Docker
-- unversioned file area for builds, statistics, other ephemeral content
-- optional PGP signing of commits
-- users can subscribe to email alerts to be notified of event types
-- private branch which are excluded from syncs until published
-- bundles group a change set (e.g. a private branch) into a single file
-- users can make their own repositories, no need for special privileges
-- works in Windows as well as Linux and other Unix-like systems
+- Synchronization via http, https, ssh, and local/network filesystems
+- Automated replication and backup
+- Git import/export and Subversion/CVS import
+- Nested checkouts to share common subtrees across related projects
+- Checkout directory not cluttered with administrative files
+- Support for Docker
+- Unversioned file area for builds, statistics, other ephemeral content
+- Optional PGP signing of commits
+- Users can subscribe to email alerts to be notified of events
+- Private branches which are excluded from syncs until published
+- Bundles group a change set (e.g. a private branch) into a single file
+- Users can make their own repositories, no need for special privileges
+- Works in Windows as well as Linux and other Unix-like systems
 
-Fossil can host the entire project development website, including the
+Fossil can host an entire project development website, including the
 download area, but it also can be used for individual projects with no
 need for a shared server.
 
@@ -49,14 +49,14 @@ See Fossil in action online:
 
 Key technical points:
 
-- unified revision history tree spans the entire repository
-- repository is a collection of artifacts identified by their checksums
-- artifacts are broadly grouped into content and structural artifacts
-- each check-in is tracked as a structural artifact known as a manifest
-- manifests primarily list the full names and checksums of each file
-- manifests can be amended by subsequent control artifacts
-- in most cases, symbolic names refer to the latest matching check-in
-- branches are implemented using propagating symbolic tags
+- Unified revision history tree spans the entire repository
+- Repository is a collection of artifacts identified by their checksums
+- Artifacts are broadly grouped into content and structural artifacts
+- Each check-in is tracked as a structural artifact known as a manifest
+- Manifests primarily list the full names and checksums of each file
+- Manifests can be amended by subsequent control artifacts
+- In most cases, symbolic names refer to the latest matching check-in
+- Branches are implemented using propagating symbolic tags
 
 ------------------------------------------------------------------------