From: Jakub Narebski Date: Mon, 14 May 2007 00:50:22 GMT Subject: Re: [PATCH] git-add: allow path limiting with -u Message-ID: <200705140250.22478.jnareb@gmail.com> In-Reply-To: <20070514003910.GA6689@coredump.intra.peff.net> Jeff King wrote: > 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 > --- > 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 > That is very nice and needed, but I actually thought about correcting SYNOPSIS to read: @@ -7,7 +7,9 @@ git-add - Add file contents to the changeset to be committed next SYNOPSIS -------- -'git-add' [-n] [-v] [-f] [--interactive | -i] [-u] [--] ... +'git-add' [-n] [-v] [-f] [--] ... +'git-add' [-n] [-v] [-f] -u [[--] ...] +'git-add' (--interactive | -i) DESCRIPTION ----------- This ensures that while git-add without -u needs explicit paths (even if it is '.'), git-add with -u can have explicit paths but doesn't need them. -- Jakub Narebski Poland