Re: [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

From: "Junio C Hamano" : Saturday, July 02, 2016 12:01 AM Junio C Hamano writes: On Fri, Jul 1, 2016 at 3:08 PM, Philip Oakley wrote: ~~~ To exclude commits reachable from a commit, a prefix '{caret}'

Re: [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

Junio C Hamano writes: > On Fri, Jul 1, 2016 at 3:08 PM, Philip Oakley wrote: ~~~ To exclude commits reachable from a commit, a prefix '{caret}' notation is used. E.g. '{caret}r1 r2' means commits reachable

Re: [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

From: "Junio C Hamano" Philip Oakley writes: Signed-off-by: Philip Oakley --- Documentation/revisions.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/revisions.txt

Re: [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

On Fri, Jul 1, 2016 at 3:08 PM, Philip Oakley wrote: >>> ~~~ >>> To exclude commits reachable from a commit, a prefix '{caret}' >>> notation is used. E.g. '{caret}r1 r2' means commits reachable >>> -from 'r2' but exclude the ones reachable

Re: [PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

Philip Oakley writes: > Signed-off-by: Philip Oakley > --- > Documentation/revisions.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt > index 131060c..87be9c4

[PATCH v2 4/4] doc: clarify that `^r1` will exclude `r1` itself

Signed-off-by: Philip Oakley --- Documentation/revisions.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index 131060c..87be9c4 100644 --- a/Documentation/revisions.txt +++