From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Richard Hansen" <rhansen@rhansen.org>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: [PATCH] doc: glossary: add entry for revision range
Date: Sun, 16 May 2021 15:37:36 -0500 [thread overview]
Message-ID: <20210516203736.1098072-1-felipe.contreras@gmail.com> (raw)
Revision ranges are one of the most pervasive concepts in Git. It belongs
in the glossary.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
Documentation/glossary-content.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index 67c7a50b96..31151277ba 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -554,6 +554,10 @@ The most notable example is `HEAD`.
[[def_revision]]revision::
Synonym for <<def_commit,commit>> (the noun).
+[[def_revision_range]]revision range::
+ A syntax to specify a list of commits, usually indicating the starting
+ and ending points. For example: `master..@`.
+
[[def_rewind]]rewind::
To throw away part of the development, i.e. to assign the
<<def_head,head>> to an earlier <<def_revision,revision>>.
--
2.31.1
next reply other threads:[~2021-05-16 20:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 20:37 Felipe Contreras [this message]
2021-05-17 7:46 ` Re* [PATCH] doc: glossary: add entry for revision range Junio C Hamano
2021-05-17 10:30 ` Felipe Contreras
2021-05-17 11:55 ` Jeff King
2021-05-17 17:22 ` Felipe Contreras
2021-05-18 6:59 ` Jeff King
2021-05-18 12:28 ` Felipe Contreras
2021-05-17 19:26 ` Junio C Hamano
2021-05-17 21:05 ` Felipe Contreras
2021-05-18 0:51 ` Junio C Hamano
2021-05-18 1:26 ` Felipe Contreras
2021-05-18 2:08 ` Jeff King
2021-05-18 2:57 ` Junio C Hamano
2021-05-18 5:20 ` Felipe Contreras
2021-05-18 5:02 ` Felipe Contreras
2021-05-18 6:55 ` Jeff King
2021-05-18 11:42 ` Felipe Contreras
2021-05-18 12:47 ` Jeff King
2021-05-18 21:09 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210516203736.1098072-1-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=rhansen@rhansen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).