git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3] glossary: add definition for overlay

From
Thomas Gummerer <t.gummerer@gmail.com>
Date
Mar 17, 2019, 20:19 UTC
Message-ID
<20190317201956.GB1216@hank.intra.tgummerer.com>
In-Reply-To
<20190312233040.GE16414@hank.intra.tgummerer.com>

Add a definition for what overlay means in the context of git, to clarify the recently introduced overlay-mode in git checkout.

Helped-by: Elijah Newren <newren@gmail.com>
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Thomas Gummerer <t.gummerer@gmail.com>
---

v3 incorporates Junios suggestions from [*1*], and clarifies that this only applies to checking out from the index or a tree-ish, and clarifies that the files are updated like in the destination directory of 'cp -R'. I thought of making the same clarification for 'rsync --delete' as well, however I think with it being explicitly specified for 'cp -R', readers should be able to deduce that we are talking about the destination directory there as well.

*1*: <xmqq5zsnh7my.fsf@gitster-ct.c.googlers.com>
 Documentation/glossary-content.txt | 9 +++++++++
 1 file changed, 9 insertions(+)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index 023ca95e7c..0f29075551 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -287,6 +287,15 @@ 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_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
+	in the destination directory.  This is the default mode in a
+	<<def_checkout,checkout>> when checking out files from the
+	<<def_index,index>> or a <<def_tree-ish,tree-ish>>.  In
+	contrast, no-overlay mode also deletes tracked files not
+	present in the source, similar to 'rsync --delete'.
+
 [[def_pack]]pack::
 	A set of objects which have been compressed into one file (to save space
 	or to transmit them efficiently).
-- 
2.21.0.225.g810b269d1a
Previous: Thomas GummererNext: Philip Oakley
Message 18 of 31 in “What's cooking in git.git (Mar 2019, #01; Wed, 6)”
  1. Junio C HamanoMar 6, 2019
  2. Denton LiuMar 6, 2019
  3. Junio C HamanoMar 6, 2019
  4. Jeff KingMar 6, 2019
  5. Junio C HamanoMar 6, 2019
  6. Duy NguyenMar 6, 2019
  7. Junio C HamanoMar 6, 2019
  8. Philip OakleyMar 7, 2019
  9. Duy NguyenMar 7, 2019
  10. Thomas GummererMar 9, 2019
  11. Elijah NewrenMar 9, 2019
  12. Thomas GummererMar 10, 2019
  13. glossary: add definition for overlayThomas Gummerer, Mar 12, 2019
  14. Duy NguyenMar 13, 2019
  15. Thomas GummererMar 15, 2019
  16. Junio C HamanoMar 13, 2019
  17. Thomas GummererMar 15, 2019
  18. glossary: add definition for overlayThomas Gummerer, Mar 17, 2019
  19. Philip OakleyMar 21, 2019
  20. Junio C HamanoMar 22, 2019
  21. Thomas GummererMar 28, 2019
  22. Junio C HamanoMar 8, 2019
  23. Johannes SchindelinMar 6, 2019
  24. Junio C HamanoMar 18, 2019
  25. Johannes SchindelinMar 6, 2019
  26. Junio C HamanoMar 6, 2019
  27. Johannes SchindelinMar 6, 2019
  28. ps/stash-in-c, was Re: What's cooking in git.git (Mar 2019, #01; Wed, 6)Johannes Schindelin, Mar 6, 2019
  29. Junio C HamanoMar 6, 2019
  30. Jonathan TanMar 6, 2019
  31. Junio C HamanoMar 7, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.