Re: [PATCH v5 09/12] doc: revisions - define `reachable`

2016-08-29 Thread Philip Oakley
From: "Jakub Narębski" W dniu 29.08.2016 o 15:21, Philip Oakley pisze: From: "Jakub Narębski" Sent: Sunday, August 28, 2016 2:01 PM W dniu 12.08.2016 o 09:07, Philip Oakley pisze: [...] +For these commands, +specifying a single revision, using the

Re: [PATCH v5 09/12] doc: revisions - define `reachable`

2016-08-29 Thread Jakub Narębski
W dniu 29.08.2016 o 15:21, Philip Oakley pisze: > From: "Jakub Narębski" > Sent: Sunday, August 28, 2016 2:01 PM >> W dniu 12.08.2016 o 09:07, Philip Oakley pisze: [...] >>> +For these commands, >>> +specifying a single revision, using the notation described in the >>>

Re: [PATCH v5 09/12] doc: revisions - define `reachable`

2016-08-29 Thread Philip Oakley
From: "Jakub Narębski" Sent: Sunday, August 28, 2016 2:01 PM W dniu 12.08.2016 o 09:07, Philip Oakley pisze: [...] History traversing commands such as `git log` operate on a set -of commits, not just a single commit. To these commands, -specifying a single revision with

Re: [PATCH v5 09/12] doc: revisions - define `reachable`

2016-08-28 Thread Jakub Narębski
W dniu 12.08.2016 o 09:07, Philip Oakley pisze: [...] > History traversing commands such as `git log` operate on a set > -of commits, not just a single commit. To these commands, > -specifying a single revision with the notation described in the > -previous section means the set of commits

[PATCH v5 09/12] doc: revisions - define `reachable`

2016-08-12 Thread Philip Oakley
Do not self-define `reachable`, which can lead to misunderstanding. Instead define `reachability` explictly. Signed-off-by: Philip Oakley --- unchanged --- Documentation/revisions.txt | 14 ++ 1 file changed, 10 insertions(+), 4 deletions(-) diff --git