[ANNOUNCE] yap: Yet Another (Git) Porcelain

[Steven Walter <stevenrwalter@gmail.com>]

After starting yap several weeks ago, I feel it has reached a level of
maturity that makes it suitable for public consumption.  yap is three
things, in increasing order of relevance:

    1) A git porcelain implemented in python
    2) A git porcelain with a friendlier, more orthogonal interface
    3) A extensible git porcelain

The third point is most interesting, because as far as the author is
aware, it is the first such project to attempt to achieve this.
Included in this distribution are plugins to create backups during
revert, make "temporary" commits, and ease interoperability with
subversion repositories.

Using git to operate on subversion-hosted repositories is a frequent use
case, and will continue to be until the world embraces git as the
awesome tool it is (keep in mind that even CVS is still in common
usage).  The git-svn tool distributed with git greatly facilitates this.
However, using git-svn requires markedly different workflows, commands,
and mental processes than does working with git-native repositories.

By leveraging the extensible nature of yap, its svn mode strives to make
a remote svn repository act and feel as much like a git repository as
possible to lessen the impedance mismatch to the user.

Yap is still very much a work-in-progress.  Patches are welcome.
Suggestions are welcome.  Bug reports are expected.  Hopefully this
tool can fill a gap in your git toolbox.

Features
--------
    * Most commands are easily and clearly reversible (commit/uncommit).  Those
      that are not are clearly marked as such.
    * Commands that have potentially unintended side-effects warn about such.
      For example, "point" will warn if moving the branch would make some
      commits reachable only through the commit log
    * SVN interoperation
        * Cloning an SVN repository is no different than cloning a git
          repository (only slower)
        * Same command to push to an SVN repo as a git repo
        * Standard workflow (yap update) is appropriate for svn-based and
          git-native setups
        * Working with "cache repositories" is supported directly.  When
          cloning a repository generated by "yap clone <svn url>", the new
          repositories is automatically configured to push back to the
          subversion repository.
-- 
-Steven Walter <stevenrwalter@gmail.com>
Freedom is the freedom to say that 2 + 2 = 4
B2F1 0ECC E605 7321 E818  7A65 FC81 9777 DC28 9E8F