On Wed, 17 Sep 2008, Nguyen Thai Ngoc Duy wrote: > On 9/17/08, Jakub Narebski <jnareb@xxxxxxxxx> wrote: >> >> Well, what I wanted to ask is if --remove-path starts from fully >> checked out repository, for example if >> >> $ git checkout --remove-path=some_large_file >> >> would checkout all files _except_ 'some_large_file'. > > No, there is no negative spec. Like I said above, --remove-path is to > remove some files based on the given spec. So "git checkout --path/--add-path/--remove-path" is porcelain interface to use (git-update-index is plumbing)? >>>> And is <pathspec> matched against full pathname, or like .gitignore >>>> rules, i.e. as full pathname if it has at least one '/' in it? >>> >>> like shell wildcard, full pathname must match. On my way back home, I >>> thought I should have removed mention of "pathspec", which behaves a >>> little bit different. >>> >>> Also those specs are relative to working directory though, so if you >>> are in b/c and want to match d, you only need to type --add-path=d >>> instead of --add-path=b/c/d. Will add this to doc. >> >> I would have thought that you follow the same rules (perhaps with >> exception of !path excluding rule) like for gitignore and gitattributes. > > Um.. never thought of gitignores/gitattributes rules before. It's a > good idea all narrowspec/gitignore/gitattributes using the same rules. Perhaps you would be able to even reuse some of implementation?... -- Jakub Narebski Poland -- 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
