projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 48bf2fa) | patch
revisions(7): clarify that most commands take a single revision range
authorJunio C Hamano <gitster@pobox.com>
Tue, 18 May 2021 00:53:37 +0000 (09:53 +0900)
committerJunio C Hamano <gitster@pobox.com>
Tue, 18 May 2021 01:08:03 +0000 (10:08 +0900)
commitf302c1e4aa09ca6120968256d65dba291990929d
tree203a2a70143a25f67f2203e97157ced3e274de62tree | snapshot
parent48bf2fa8bad054d66bd79c6ba903c89c704201f7commit | diff
revisions(7): clarify that most commands take a single revision range

Sometimes new people are confused by how a revision "range" works,
in that it is not a random collection of commits but a set of
commits that are all connected to each other, and most Git commands
work on a single such "range".

Give an example to clarify it.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/revisions.txt diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.