From: "Jakub Narębski"
W dniu 2016-07-13 o 00:11, Philip Oakley pisze:
From: "Junio C Hamano"
[...]
I actually think this is a good place to have them described.
^ is about specifying a single commit. These two are
not that (you can say HEAD^2^@ but you cannot say HEAD^@^2, for
example).
W dniu 2016-07-13 o 00:11, Philip Oakley pisze:
> From: "Junio C Hamano"
[...]
>> I actually think this is a good place to have them described.
>> ^ is about specifying a single commit. These two are
>> not that (you can say HEAD^2^@ but you cannot say HEAD^@^2, for
>> example).
>
> These two ar
From: "Junio C Hamano"
Marc Branchaud writes:
+The '{caret}' (caret) notation
+~~~
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 from 'r1'
On Tue, Jul 12, 2016 at 10:41:35PM +0100, Philip Oakley wrote:
> > > +The '{caret}' (caret) notation
> > > +~~~
> > > To exclude commits reachable from a commit, a prefix '{caret}'
> > > notation is used. E.g. '{caret}r1 r2' means commits reachable
> > > from 'r2
From: "Marc Branchaud"
On 2016-07-11 04:25 PM, Philip Oakley wrote:
While there, also break out the other shorthand notations and
add a title for the revision range summary (which also appears
in git-rev-parse, so keep it mixed case).
Signed-off-by: Philip Oakley
---
Documentation/revisions
Marc Branchaud writes:
>> +The '{caret}' (caret) notation
>> +~~~
>> 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 from 'r1'.
>
> All of
On 2016-07-11 04:25 PM, Philip Oakley wrote:
While there, also break out the other shorthand notations and
add a title for the revision range summary (which also appears
in git-rev-parse, so keep it mixed case).
Signed-off-by: Philip Oakley
---
Documentation/revisions.txt | 23 +++
7 matches
Mail list logo
