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

[RFC PATCH 5/5] ref-filter: add docs for new options

From
Olga Telezhnaya <olyatelezhnaya@gmail.com>
Date
Nov 9, 2018, 07:44 UTC
Message-ID
<01020166f76d851b-3a0f5414-48ce-4172-8200-0a59fd3f66d9-000000@eu-west-1.amazonses.com>
In-Reply-To
<01020166f76d845f-1a02a31e-5094-4b27-974d-a23811066c58-000000@eu-west-1.amazonses.com>

Add documentation for formatting options objectsize:disk and deltabase.

Signed-off-by: Olga Telezhnaia <olyatelezhnaya@gmail.com>
---
 Documentation/git-for-each-ref.txt | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index 901faef1bfdce..22d2ff88110cd 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -128,13 +128,18 @@ objecttype::
 
 objectsize::
 	The size of the object (the same as 'git cat-file -s' reports).
-
+	Append `:disk` to get the size, in bytes, that the object takes up on
+	disk. See the note about on-disk sizes in the `CAVEATS` section below.
 objectname::
 	The object name (aka SHA-1).
 	For a non-ambiguous abbreviation of the object name append `:short`.
 	For an abbreviation of the object name with desired length append
 	`:short=<length>`, where the minimum length is MINIMUM_ABBREV. The
 	length may be exceeded to ensure unique object names.
+deltabase::
+	If the object is stored as a delta on-disk, this expands to the 40-hex
+	sha1 of the delta base object. Otherwise, expands to the null sha1
+	(40 zeroes). See `CAVEATS` section below.
 
 upstream::
 	The name of a local ref which can be considered ``upstream''
@@ -361,6 +366,20 @@ This prints the authorname, if present.
 git for-each-ref --format="%(refname)%(if)%(authorname)%(then) Authored by: %(authorname)%(end)"
 ------------
 
+CAVEATS
+-------
+
+Note that the sizes of objects on disk are reported accurately, but care
+should be taken in drawing conclusions about which refs or objects are
+responsible for disk usage. The size of a packed non-delta object may be
+much larger than the size of objects which delta against it, but the
+choice of which object is the base and which is the delta is arbitrary
+and is subject to change during a repack.
+
+Note also that multiple copies of an object may be present in the object
+database; in this case, it is undefined which copy's size or delta base
+will be reported.
+
 SEE ALSO
 --------
 linkgit:git-show-ref[1]

--
https://github.com/git/git/pull/552
Previous: Olga TelezhnayaNext: Junio C Hamano
Message 5 of 15 in “ref-filter: add objectsize:disk option”
  1. 1/5 ref-filter: add objectsize:disk optionOlga Telezhnaya, Nov 9, 2018
  2. 3/5 ref-filter: add deltabase optionOlga Telezhnaya, Nov 9, 2018
  3. 4/5 ref-filter: add tests for deltabaseOlga Telezhnaya, Nov 9, 2018
  4. 2/5 ref-filter: add tests for objectsize:diskOlga Telezhnaya, Nov 9, 2018
  5. 5/5 ref-filter: add docs for new optionsOlga Telezhnaya, Nov 9, 2018
  6. Junio C HamanoNov 12, 2018
  7. Junio C HamanoNov 12, 2018
  8. Johannes SchindelinNov 12, 2018
  9. Jeff KingNov 12, 2018
  10. Junio C HamanoNov 13, 2018
  11. Оля ТележнаяNov 20, 2018
  12. Junio C HamanoNov 21, 2018
  13. Johannes SchindelinNov 22, 2018
  14. Junio C HamanoNov 24, 2018
  15. Jeff KingNov 12, 2018

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.