Make `vcsh list` even more resilient ;)

[code/vcsh.git] / doc / vcsh.1.ronn

diff --git a/doc/vcsh.1.ronn b/doc/vcsh.1.ronn
index 17be1a9ba72fe8bf6e517475bfa49ae0161425f1..0fbead9a78c4f30ce0e1d02680a913249c49dbf7 100644 (file)
--- a/doc/vcsh.1.ronn
+++ b/doc/vcsh.1.ronn
@@ -25,6 +25,8 @@ vcsh(1) - manage config files in $HOME via fake bare git repositories
 
 `vcsh` setup <repo>
 
 
 `vcsh` setup <repo>
 

+`vcsh` which <substring>
+

 `vcsh` write-gitignore <repo>
 
 `vcsh` <repo> <gitcommand>
 `vcsh` write-gitignore <repo>
 
 `vcsh` <repo> <gitcommand>


@@ -98,6 +100,9 @@ an interactive user.
 * setup:
   Set up repository with recommended settings.
 
 * setup:
   Set up repository with recommended settings.
 

+* which <substring>:
+  Find <substring> in name of any tracked file.
+

 * write-gitignore:
   Write .gitignore.d/<repo> via git ls-files.
 
 * write-gitignore:
   Write .gitignore.d/<repo> via git ls-files.
 


@@ -155,6 +160,12 @@ You can put any and all commands into this config file and they will be executed
 
 None are known at this time, but reports and/or patches are more than welcome.
 
 
 None are known at this time, but reports and/or patches are more than welcome.
 

+## KNOWN ISSUES
+
+As of this writing (June 2012), `vcsh` does not work with `git submodule` due
+to limitations within `git`. Depending on when you are reading this, you might
+want to consider upgrading.
+

 ## HISTORY
 
 Like most people, the author initially made do with a single repository for all
 ## HISTORY
 
 Like most people, the author initially made do with a single repository for all


@@ -175,7 +186,7 @@ This manpage and `vcsh` itself were written by Richard "RichiH" Hartmann.
 
 Copyright 2011-2012 Richard Hartmann <richih.mailinglist@gmail.com>
 
 
 Copyright 2011-2012 Richard Hartmann <richih.mailinglist@gmail.com>
 

-Licensed under the GNU GPL version 3 or higher.
+Licensed under the GNU GPL version 2 or higher.

 
 https://github.com/RichiH/vcsh
 
 
 https://github.com/RichiH/vcsh