aboutsummaryrefslogtreecommitdiffstats
path: root/commit.h
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2021-05-18 09:53:37 +0900
committerJunio C Hamano <gitster@pobox.com>2021-05-18 10:08:03 +0900
commitf302c1e4aa09ca6120968256d65dba291990929d (patch)
tree203a2a70143a25f67f2203e97157ced3e274de62 /commit.h
parentGit 2.31.1 (diff)
downloadgit-f302c1e4aa09ca6120968256d65dba291990929d.tar.gz
git-f302c1e4aa09ca6120968256d65dba291990929d.zip
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>
Diffstat (limited to 'commit.h')
0 files changed, 0 insertions, 0 deletions