From: scs@eskimo.com (Steve Summit)
To: git@vger.kernel.org
Subject: suggestion for git glossary: "ort"
Date: Sat, 16 Apr 2022 11:07:09 -0400 [thread overview]
Message-ID: <2022Apr16.1107.scs.0007@quinine2.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
I kept seeing references to "ort" in the git source code, and I
had no idea what it meant. Grepping around in the Documentation
tree eventually revealed: it's a new merge strategy! Suggested
glossary patch attached; feel free to improve.
[-- Attachment #2: glossary-content.txt.patch --]
[-- Type: text/plain, Size: 833 bytes --]
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index aa2f41f..cb0726f 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -287,6 +287,13 @@ This commit is referred to as a "merge commit", or sometimes just a
origin/name-of-upstream-branch, which you can see using
`git branch -r`.
+[[def_ort]]ort::
+ The default merge strategy when pulling or merging one branch.
+ An acronym for "Ostensibly Recursive's Twin", due to the fact
+ that it was written as a replacement for the previous default
+ algorithm, `recursive`. See linkgit:git-merge[1], section
+ "Merge Strategies".
+
[[def_overlay]]overlay::
Only update and add files to the working directory, but don't
delete them, similar to how 'cp -R' would update the contents
next reply other threads:[~2022-04-16 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 15:07 Steve Summit [this message]
2022-04-16 22:42 ` suggestion for git glossary: "ort" Junio C Hamano
2022-04-18 10:16 ` Steve Summit
2022-04-18 17:43 ` Junio C Hamano
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=2022Apr16.1107.scs.0007@quinine2.home \
--to=scs@eskimo.com \
--cc=git@vger.kernel.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).