[PATCH] Small grammar fix

as common as advice.) Signed-off-by: Greg Price pr...@mit.edu --- Documentation/config.txt | 2 +- t/t7512-status-help.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index e452ff8..dbb2faf 100644 --- a/Documentation

[PATCH] describe: Document --match pattern format

It's not clear in git-describe(1) what kind of pattern should be passed to --match. Fix that. Signed-off-by: Greg Price pr...@mit.edu --- Documentation/git-describe.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/git-describe.txt b/Documentation/git

[PATCH] Fix .git/refs stragglers

A couple of references still survive to .git/refs as a tree of all refs. Fix one in docs, one in a -h message, one in a -h message quoted in docs. Signed-off-by: Greg Price pr...@mit.edu --- Documentation/config.txt | 2 +- Documentation/gitcli.txt | 9 + builtin/describe.c | 4

[PATCH 2/2] describe: Exclude --all --match=PATTERN

is an oxymoron anyway, so just forbid it. Signed-off-by: Greg Price pr...@mit.edu --- This should be applied after the preceding patch; I mistakenly omitted the '1/2' in its subject line. Documentation/git-describe.txt | 3 ++- builtin/describe.c | 3 +++ 2 files changed, 5 insertions

Re: [PATCH 2/2] describe: Exclude --all --match=PATTERN

--tags in the error message. Greg From 66f985b2510c870e62e313732de4b6709894b074 Mon Sep 17 00:00:00 2001 From: Greg Price pr...@mit.edu Date: Sun, 3 Mar 2013 12:19:57 -0800 Subject: [PATCH] describe: Better error message on --all --match The reason they conflict is that --all means (a) allow

Re: [PATCH 2/2] describe: Exclude --all --match=PATTERN

On Sun, Mar 03, 2013 at 01:15:21PM -0800, Junio C Hamano wrote: Greg Price pr...@mit.edu writes: It seems to me that --all says two things: (a) allow unannotated (rather than only annotated) (b) allow refs of any name (rather than only tags) With --match, particularly because

[PATCH] add: cut redundant require_pathspec logic

If take_worktree_changes is true, then the logic around option_with_implicit_dot ensures argc is positive by this point. So require_pathspec never has an effect. Signed-off-by: Greg Price pr...@mit.edu --- builtin/add.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH] add: Clarify documentation of -A and -u

the word 'all'), and then describe the contrast separately. Signed-off-by: Greg Price pr...@mit.edu --- Documentation/git-add.txt | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt index 388a225..f89d920

Re: [PATCH] add: Clarify documentation of -A and -u

tree. These are the shortest in the discussion so far, and I think they're also the clearest. Then follow both with the If no pathspec paragraph. I just noticed that the paragraph actually needs a small modification to fit '-A', too. New patch below. Greg From: Greg Price pr...@mit.edu Date