On Sun, May 13, 2007 at 12:35:24PM +0200, Jakub Narebski wrote: > Do git-add *needs* path specifier (even if it is '.') also for `-u'? > The changes in documentation were to reflect that `-u' is incompatibile > with explicit paths, or that `-u' does not require explicit paths > contrary to git-add without `-u'. Sorry, I don't understand if you are asking that question, or if you are asking if the documentation needs to clarify that point. The answer to the first is "no", the path limiting works exactly as it does for every other command: no path specifier indicates the whole tree. If you are concerned about the latter, do you mean something like this: -- >8 -- Documentation/git-add: clarify -u with path limiting Signed-off-by: Jeff King <peff@xxxxxxxx> --- diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt index ea27018..27b9c0f 100644 --- a/Documentation/git-add.txt +++ b/Documentation/git-add.txt @@ -57,8 +57,11 @@ OPTIONS the index. -u:: - Update all files that git already knows about. This is what - "git commit -a" does in preparation for making a commit. + Update only files that git already knows about. This is similar + to what "git commit -a" does in preparation for making a commit, + except that the update is limited to paths specified on the + command line. If no paths are specified, all tracked files are + updated. \--:: This option can be used to separate command-line options from - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
