gdiff 0.0.1

data/CHANGELOG

@@ -0,0 +1,7 @@
+0.0.1
+  * Improved documentation
+  * Releasing as a .gem, .tar.gz, .tar.bz2, and .zip.
+  * Improved interface
+
+0.0.0
+  * Initial Release

data/COPYING.suffix_array

@@ -0,0 +1,278 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.

data/LICENSE.suffix_array

@@ -0,0 +1,17 @@
+FastCST -- A tool for revision control.
+
+Copyright (C) 2004-2005  Zed A. Shaw
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

data/README

@@ -0,0 +1,40 @@
+# gdiff / gpatch
+
+## Description
+An implementation of the gdiff protocol.
+[Protocol description](http://www.w3.org/TR/NOTE-gdiff-19970901)
+
+## Find it at 
+
+  http://ruby.brian-schroeder.de/gdiff/
+
+## Installation:
+
+    wget http://ruby.brian-schroeder.de/gdiff/releases/gdiff-0.0.1.tar.bz2
+    tar -xvvjf gdiff-0.0.1.tar.bz2
+    cd gdiff-0.0.1
+    ruby setup.rb
+
+## Usage:
+
+    gdiff file_a file_b > patch
+    gpatch file_a patch > file_b_from_patch
+
+### or as a library:
+
+    require 'gdiff'
+
+    File.open("patch", "wb") do | patch |
+      patch << Diff::GDiff.diff(File.read("file_a"), File.read("file_b")).pack
+    end
+
+    File.open("file_b_from_patch", "wb") do | file_b_2 |
+      file_b_2 << Diff::GDiff.unpack(File.read("patch")).apply_to(File.read("file_a"))
+    end
+  
+## Authors
+This was implemented by Brian Schroeder with the help of Zed Shaws wonderfull
+suffix-tree extension.
+
+## License
+GPL and ruby license if applicable (I have to ask zed).

data/README.suffix_array

@@ -0,0 +1,274 @@
+== Fast Change Set Tool
+
+FastCST is a change set tool I created to experiment with
+ideas in change management, distributed development, and alternatives to existing
+tools.
+
+== Current Features
+
+FastCST is an evolving tool that you probably shouldn't use quite yet for
+anything serious.  It does support a wide range of features, but since I
+started in in March 2005 it's not fully tested yet.
+
+The current laundry list of features are:
+
+* Complete changesets that are very simple by design and encode complete
+  cohesive changes.
+* Extensible meta-data for changesets.
+* A simple to use repository that should be easy for any other languages to read.
+* All revisions are uniquely identified by a UUID to avoid clashing.
+* Ability to undo any applied revision.
+* You can publish your repository to an FTP site efficiently.
+* Directly share your repository for quick small-scale sharing without FTP.
+* Anyone can download the latest revisions from an FTP or HTTP site.
+* Send/receive changesets through e-mail including human readable meta-data.
+* Transaction oriented operation.
+* Remarkably fast operation considering there's been no optimization done and it's written in Ruby.
+* A reasonable shell prompt so you don't have to type 'fcst' in front of everything.
+* A working plugins feature letting you implement your own commands, with an example
+  command that creates release archives.
+* A working "triggers" feature so you can easily wrap commands with your own logic.
+* Ability to attach external files to distribute with your changesets (not tested much).
+* Disposition references so you can reference bug trackers, web sites, mailing list posts, etc.
+* 95% pure Ruby.
+* A unique delta algorithm that uses suffix arrays and produces smaller deltas than most other
+  delta algorithms without sacrificing speed much.
+* A painstakingly consistent command interface with extensive help for each option.
+* The beginning of a merge feature that let's you merge without needing to reference history.
+* An "index" command that will use suffix arrays to index your files and let you find where
+  text is mentioned.  This will turn into an optimization and an advanced search feature.
+* Simple and consistent aborting and undo so you can trash your source in the comfort of your
+  own stupidity and still recover.
+* Completely redesigned YAML format that avoids using !ruby object loading and uses only
+  native types found in all languages.  This avoids some security concerns, but YAML needs
+  a means of telling it to NOT load arbitrary objects.  Still searching, but I may have to 
+  dump YAML if I can't fix it.
+* Makes a reasonable attempt to deal with symlinks and directories.  It treats directories
+  as out of band data and simply fixes them up at the end of the application process.  This
+  is very handy since you can just glance at the meta-data to find out if someone is deleting
+  your favorite source tree.
+
+
+== Missing Features
+
+There's still quite a lot of stuff missing that I want to put into FastCST, but these are
+the big ones that it needs before it's useful:
+
+* Merging is implemented, but conflict resolution is not yet.  It currently will not let
+  you resolve conflicts and refuses to do the merge.
+* Recovering individual files from the repository.  This is needed to get conflicts working.
+* Better security protections like not using YAML for the journal file or somehow restricting
+  what objects can be loaded (that thing is like giving a toddler a shot-gun).
+* Digitally signed and verified revisions so people can confirm who sent the revision.
+* Improved safety checks.  It's pretty good now, but things like applying a delta is still
+  not as safe as I'd like.
+
+Some of the things I'd like to implement are:
+
+* Connecting with FAM or Dazuko to let FastCST track your actions and warn about bad stuff.
+* Flexible command aliasing that lets you create alternative commands.
+* Using mDNS to let people quickly and painlessly find repositories and other developers.
+* Hooking into DamageControl and the RSCM library.
+
+If you have any suggestions for these or for other features you want then go ahead and
+contact me at zedshaw AT zedshaw DOT com.
+
+== Security Warnings
+
+DO NOT ACCEPT CHANGESETS FROM PEOPLE YOU DO NOT KNOW.  Since there's no digital signature
+capabilities this means nobody except yourself.  The reason why is because there are many
+places whe YAML is used, but YAML doesn't provide a mechanism for restricting what can
+be loaded when unmarshalling Ruby structures.  It would be no problem for someone to create
+a meta-data or journal file with a bit of code to destroy your world.
+
+Another really big caution is please don't use this thing on any source you feel is really
+important.  It is still mostly ALPHA stage so there's a very good chance that you'll destroy
+your world if you use it.  Especially important is that the delta algorithm is fairly new
+and the suffix array library needs to be audited more.
+
+Finally, it uses POP3 and FTP with bare passwords.  This is mostly because I'm not sure how
+to get the Net::POP and Net::FTP stuff to use APOP and/or SSL.  For the most part I'm just
+tunneling the protocols through SSH to my servers.
+
+
+== License
+
+Copyright (C) 2004-2005  Zed A. Shaw
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+=== Building
+
+The script that does everything is called "fcst", and the Rakefile is setup to build
+a completely stand-alone version.  This is the version that you can run with only a
+basic ruby 1.8 install rather than installing all the files in your Ruby directories.
+
+Building the fcst script this way requires simply typing "rake" in the source
+directory.  When the build is done you'll have a single ruby script in build/fcst.
+
+
+==== Debian Notes
+
+The build has been tested on ArchLinux and Debian, but to get it to build or 
+work under Debian you'll need to do some magic apt-get work:
+
+1.  Remove anything remotely related to ruby.  The package layout changed recently
+    so this is necessary to get it to reinstall correctly.
+2.  apt-get install ruby (not ruby1.8).  If you're on the right version of Debian
+    (of the 100) you should get the 1.8 stuff with all the goodies.
+3.  Finally make sure you have these packages as well:
+    * rake
+    * ruby1.8-dev (yes, specify the 1.8 this time)
+    * libtest-unit-ruby (no 1.8 this time)
+
+Once you do this you can then use the "rake" command to build everything and get
+your stand-alone build/fcst script.
+
+
+=== Installing
+
+You can also "install" the fcst script in the normal ruby way using the setup.rb 
+script.  This installs the required libraries in your Ruby installation's directories
+and thus requires root access.  
+
+The first thing you need to do is go into the software directory and install the 
+PluginFactory, ruby-guid, and rubymail tar.gz sources you find.  Each project has
+its own install method, but most use the standard setup.rb or similar.  Read their
+instructions.
+
+Then installing is done with "ruby setup.rb" in the FastCST source directory.  This
+will install the fcst script in your standard bin directory and the required library
+files in your standard Ruby setup.  You'll probably need root access for this.
+
+
+== Getting Started
+
+FastCST is designed to be easy to use without restricting your ability to
+get stuff done.  This means that most commands are very simple and follow
+a consistent pattern of operation with extensive help.  It also means that,
+if you don't like a command or need an additional feature then you can easily
+write your own.
+
+The fcst script has two modes of operation:
+
+* shell mode -- This lets you run commands in a small little shell so that
+  you don't have to keep typing 'fcst' before you do things.
+* command line mode -- You can also just put the command after the fcst
+  script in your normal shell and it will run it directly.
+   
+The current shell is very primitive and doesn't support readline or many other
+nice features.
+
+If you want to get a list of commands then type 'help'.  It actually isn't 
+a command, but the error message for giving an invalid command is to print
+a list of all the commands available.
+
+
+=== Available Commands
+
+FastCST currently supports the following commands:
+
+* abort -- Aborts any currently in-process revision
+* apply -- Applies a child revision to the current revision 
+* attach -- Attaches a file to the current in-process revision 
+* begin -- Starts a new in-process revision
+* disp -- Adds a "disposition" reference to the in-process revision
+* env -- Lists, searches, sets, and deletes environment variables
+* finish -- Finalizes an in-process revision
+* get -- Gets the latest published revisions from a URL
+* init -- Sets up a new .fastcst repository in the current directory
+* list -- Let's you list revisions and your current revision path
+* log -- Adds a log line to the in-process revision (think Change Log)
+* publish -- Publishes your repository to an FTP site so others can use get
+* read -- Reads your "pending revision inbox" which contains received revisions
+* recv -- Receives revisions from a POP3 account and stores them for read
+* send -- Sends a chosen revision to a chosen person
+* show -- Shows information about a revision, or the in-process revision
+* status -- Gives a quick status of the current state of things
+* undo -- Rolls back the most recent apply
+* merge -- Basic revision merging.  Does not handle conflicts yet (will abort).
+* index -- Basic suffix array based searching through files.
+
+All commands have a -h option, and will also complain if everything isn't perfect
+when you run them.  To get the list of commands just you can use ? or help.
+
+
+=== Your First Repository
+
+FastCST uses a "project local" repository design.  This means that, rather
+than keeping everything in one master directory, it creates one directory
+for each project.  The directory is called .fastcst and simply sits at the
+top of your source files.
+
+What we're going to do is actually get the latest version of FastCST using
+fcst.  Make sure you've downloaded the script or built your own and then 
+do this:
+
+1.  Create an empty directory and cd into it.
+2.  Run fcst
+3.  > init -e <your e-mail> -n <your name> -p fastcst
+4.  > get -u http://www.zedshaw.com/fastcst/repository
+5.  > list
+6.  > show -r root
+7.  > apply -r root
+
+You now have the root revision of the FastCST 0.6 stuff.  The list and show commands
+aren't necessary, just a good idea so you don't apply something that will cause you
+damage.
+
+One current limit of fastcst is that when you get a remote repository it doesn't
+ask you to apply all the revisions so you can sync up.  I'm holding off on that
+feature until I get the merging algorithm done.  Until then, feel free to 
+apply the patches and play with the apply/merge/undo stuff.
+
+==== Other Things To Try
+
+Here's some other stuff for you to try out:
+
+1.  You do not need to have an empty directory to put files under fcst control.
+2.  Make a changeset by using begin/finish.  You can run begin, make some changes, and then
+    run finish to create the revision.
+3.  Most commands that take a -r also take a -i so you can be specific about which revision
+    to use.  Revision names are mostly just for weak humans who can't handle uuids.
+4.  Use list, show, and status religiously to figure out what's going on.
+5.  You can easily send a revision to someone else.  Use send to give them one, and then
+    recv to get them from a POP3 account.  It works like e-mail where they are downloaded,
+    and then you use 'read' to pick which ones you really want added to your repository.
+6.  Most commands will look for settings in the environment and use them as defaults.
+    Try running a command without parameters and read the lines that talk about not finding
+    a setting in the environment.  For example, recv will look for 'POP3 Host' so you can
+    do "env -s 'POP3 Host' -v mail.myserver.com:110" and it will never bug you again.  If you
+    need to use a different one temporarily, then specifying the option will override the
+    environment setting.
+7.  If you've got an FTP server and web server to play with, then you can try the publish/get
+    commands.
+8.  All commands take a -h option so you can get extensive help.
+9.  Try the index command.  Run it once without options to build the index, then check -h.
+
+=== More Detailed Documentation
+
+This README just gives you some quick advice to get you started.  Better
+documentation is available at http://www.zedshaw.com/projects/fastcst including
+the full API documentation (which is also in doc/rdoc), tutorials, and several
+other nice things.
+
+=== Reporting Bugs
+
+Feel free to contact me at zedshaw AT zedshaw DOT com with any bug reports you have.
+You may also find the latest release information at 
+http://www.zedshaw.com/projects/fastcst as well as contact me on irc.freenode.org
+in the #ruby-lang or #rubyonrails channel.
+