summaryrefslogtreecommitdiff
path: root/Documentation
AgeCommit message (Collapse)Author
2026-01-15Git 2.53-rc0v2.53.0-rc0Junio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-01-12The 17th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-01-12Merge branch 'ja/doc-synopsis-style-more'Junio C Hamano
More doc style updates. * ja/doc-synopsis-style-more: doc: convert git-remote to synopsis style doc: convert git stage to use synopsis block doc: convert git-status tables to AsciiDoc format doc: convert git-status to synopsis style doc: fix t0450-txt-doc-vs-help to select only first synopsis block
2026-01-08The 16th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-01-06The 15th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-30The 14th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-30Merge branch 'mh/doc-core-attributesfile'Junio C Hamano
Doc update. * mh/doc-core-attributesfile: docs: note the type of core.attributesfile
2025-12-30Merge branch 'jt/doc-rev-list-filter-provided-objects'Junio C Hamano
Document "rev-list --filter-provided-objects" better. * jt/doc-rev-list-filter-provided-objects: docs: clarify git-rev-list(1) --filter behavior
2025-12-30Merge branch 'jt/repo-struct-more-objinfo'Junio C Hamano
More object database related information are shown in "git repo structure" output. * jt/repo-struct-more-objinfo: builtin/repo: add object disk size info to structure table builtin/repo: add disk size info to keyvalue stucture output builtin/repo: add inflated object info to structure table builtin/repo: add inflated object info to keyvalue structure output builtin/repo: humanise count values in structure output strbuf: split out logic to humanise byte values builtin/repo: group per-type object values into struct
2025-12-28The 13th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-28Merge branch 'ja/doc-misc-fixes'Junio C Hamano
Various documentation fixes. * ja/doc-misc-fixes: doc: correct minor wording issues doc: fix asciidoc markup issues in several files
2025-12-28Merge branch 'jc/doc-commit-signoff-config'Junio C Hamano
Documentation update. * jc/doc-commit-signoff-config: signoff-option: linkify the reference to gitfaq commit: document that $command.signoff will not be added
2025-12-23The 12th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-23Merge branch 'ds/doc-scalar-config'Junio C Hamano
Documentation updates. * ds/doc-scalar-config: scalar: document config settings scalar: alphabetize and simplify config scalar: remove stale config values scalar: use index.skipHash=true for performance scalar: annotate config file with "set by scalar"
2025-12-22The 11th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-22Merge branch 'kh/doc-replay-updates'Junio C Hamano
"git replay" documentation updates. * kh/doc-replay-updates: doc: replay: link section using markup replay: improve --contained and add to doc doc: replay: mention no output on conflicts
2025-12-21doc: convert git-remote to synopsis styleJean-Noël Avila
- Switch the synopsis to a synopsis block which will automatically format placeholders in italics and keywords in monospace - Use _<placeholder>_ instead of <placeholder> in the description - Use `backticks` for keywords and more complex option descriptions. The new rendering engine will apply synopsis rules to these spans. - also convert first sentences to imperative mood where applicable Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-21doc: convert git stage to use synopsis blockJean-Noël Avila
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-21doc: convert git-status tables to AsciiDoc formatJean-Noël Avila
Instead of plain text tables with hand formatting, take advantage of asciidoc's table syntax to let the renderer do the heavy lifting and make the tables more maintainable and translatable. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-21doc: convert git-status to synopsis styleJean-Noël Avila
Also convert unformatted lists to proper AsciiDoc lists. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-20doc: correct minor wording issuesJean-Noël Avila
* use imperative mood for consistency in options descriptions * add missing parenthesis * reword verbose phrase in git-repack.adoc Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-20doc: fix asciidoc markup issues in several filesJean-Noël Avila
* fix incorrect use of backticks for markup in git-checkout.adoc, git-worktree.adoc * switch tabs to spaces in git-send-email.adoc list items Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-19signoff-option: linkify the reference to gitfaqJunio C Hamano
The GitFAQ is a proper manual page in the section 7, so refer to it using the usual linkgit:stuff[7] syntax. Helped-by: Kristoffer Haugsbakk Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-18docs: note the type of core.attributesfileMatthew Hughes
The previous wording: > Path expansions are made the same way as for `core.excludesFile`. required one to check the docs for 'core.excludesFile' and from there the definition of the pathname variable type to understand the path expansion behaviour of this variable. Instead, just link directly to the pathname type. This change is basically the same rewording as was done to 'core.excludesFile' in dca83abd (config: describe 'pathname' value type, 2016-04-29). Signed-off-by: Matthew Hughes <matthewhughes934@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-18builtin/repo: add disk size info to keyvalue stucture outputJustin Tobler
Similar to a prior commit, extend the keyvalue and nul output formats of the git-repo(1) structure command to additionally provide info regarding total object disk sizes by object type. Signed-off-by: Justin Tobler <jltobler@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-18builtin/repo: add inflated object info to keyvalue structure outputJustin Tobler
The structure subcommand for git-repo(1) outputs basic count information for objects and references. Extend this output to also provide information regarding total size of inflated objects by object type. For now, object size by object type info is only added to the keyvalue and nul output formats. In a subsequent commit, this info is also added to the table format. Signed-off-by: Justin Tobler <jltobler@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-18commit: document that $command.signoff will not be addedJunio C Hamano
Every now and then we see this coming up on the list. Let's help new contributors who are not aware of past discussions by clearly documenting our past consensus. Helped-by: brian m. carlson <sandals@crustytoothpaste.net> Helped-by: Elijah Newren <newren@gmail.com> Helped-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-17The 10th batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-17Merge branch 'kh/doc-send-email-paragraph-fix'Junio C Hamano
Docfix. * kh/doc-send-email-paragraph-fix: doc: send-email: fix broken list continuation
2025-12-17Merge branch 'mh/doc-config-gui-gcwarning'Junio C Hamano
Docfix. * mh/doc-config-gui-gcwarning: config: document 'gui.GCWarning'
2025-12-17Merge branch 'kh/doc-pre-commit-fix'Junio C Hamano
Docfix. * kh/doc-pre-commit-fix: doc: join default pre-commit paragraphs
2025-12-16The ninth batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-16docs: clarify git-rev-list(1) --filter behaviorJustin Tobler
When using the --filter option for git-rev-list(1), objects that are explicitly provided ignore filters and are always printed unless the --filter-provided-objects option is also specified. Clarify this behavior in the documentation. Signed-off-by: Justin Tobler <jltobler@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-16scalar: document config settingsDerrick Stolee
Add user-facing documentation that justifies the values being set by 'scalar clone', 'scalar register', and 'scalar reconfigure'. Helped-by: Junio C Hamano <gitster@pobox.com> Helped-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Derrick Stolee <stolee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-14The eighth batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-14Merge branch 'je/doc-data-model'Junio C Hamano
Docfix. * je/doc-data-model: doc: remove stray text in Git data model
2025-12-14Merge branch 'lo/repo-struct-z'Junio C Hamano
"git repo struct" learned to take "-z" as a synonym to "--format=nul". * lo/repo-struct-z: repo: add -z as an alias for --format=nul to git-repo-structure repo: use [--format=... | -z] instead of [-z] in git-repo-info synopsis repo: remove blank line from Documentation/git-repo.adoc
2025-12-14Merge branch 'je/doc-pull'Junio C Hamano
Doc fixup. * je/doc-pull: doc: git-pull: fix 'git --rebase abort' typo
2025-12-14doc: replay: link section using markupKristoffer Haugsbakk
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-14replay: improve --contained and add to docKristoffer Haugsbakk
There is no documentation for `--contained`. Start by copying the text from `replay_options` in `builtin/ replay.c`. But some people think that the existing text is a bit unclear; what does it mean for a branch to be contained in a revision range? Let’s include the implied commits here: the branches that point at commits in the range. Also use “update” instead of “advance”. “Update” is the verb commonly used in this context. Helped-by: Phillip Wood <phillip.wood@dunelm.org.uk> Helped-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-14doc: replay: mention no output on conflictsKristoffer Haugsbakk
Some commands will produce output on stderr if there are conflicts, but git-replay(1) is completely silent. Explicitly spell that out. Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-09The seventh batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-09Merge branch 'en/replay-doc-revision-range'Junio C Hamano
The use of "revision" (a connected set of commits) has been clarified in the "git replay" documentation. * en/replay-doc-revision-range: Documentation/git-replay.adoc: fix errors around revision range
2025-12-09config: document 'gui.GCWarning'Matthew Hughes
While investigating the config options set by 'scalar' I noticed this one wasn't documented. Signed-off-by: Matthew Hughes <matthewhughes934@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-09doc: send-email: fix broken list continuationKristoffer Haugsbakk
The list continuation has to be “immediately adjacent to the block being attached”.[1] [1]: https://web.archive.org/web/20251208172615/https://docs.asciidoctor.org/asciidoc/latest/lists/continuation/ Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-08doc: join default pre-commit paragraphsKristoffer Haugsbakk
Join two paragraphs that start with the standard “The default <hook>, when enabled” into one and put it at the end of the “pre-commit” section. The trailing whitespace paragraph was added in the first commit for the doc, in 6d35cc76 (Document hooks., 2005-09-02). Then 3e14dd2c (mention use of "hooks.allownonascii" in "man githooks", 2019-02-20) updated the “pre-commit” section to mention the non-ASCII check that was added in d00e364d.[1] But this paragraph was added one-past the original “default” paragraph, after the env. variable paragraph, and starts exactly the same. That causes the flow of this section to feel off (paragraphs in order): 1. Invoked by <cmd> and what parameters it takes 2. The default 'pre-commit' hook catches introduction of trailing whitespace 3. `GIT_EDITOR=:` 4. The default pre-commit' hook catches introduction of non-ASCII filenames Let’s instead join these two paragrahs and explain the whole behavior of the default script. † 1: Extend sample pre-commit hook to check for non ascii filenames, 2009-05-19 Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-05The sixth batchJunio C Hamano
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-12-05Merge branch 'cc/fast-import-strip-if-invalid'Junio C Hamano
"git fast-import" learns "--strip-if-invalid" option to drop invalid cryptographic signature from objects. * cc/fast-import-strip-if-invalid: fast-import: add 'strip-if-invalid' mode to --signed-commits=<mode> commit: refactor verify_commit_buffer() fast-import: refactor finalize_commit_buffer()
2025-12-05Merge branch 'kh/doc-committer-date-is-author-date'Junio C Hamano
The "--committer-date-is-author-date" option of "git am/rebase" is a misguided one. The documentation is updated to discourage its use. * kh/doc-committer-date-is-author-date: doc: warn against --committer-date-is-author-date
2025-12-05Merge branch 'en/xdiff-cleanup-2'Junio C Hamano
Code clean-up. * en/xdiff-cleanup-2: xdiff: rename rindex -> reference_index xdiff: change rindex from long to size_t in xdfile_t xdiff: make xdfile_t.nreff a size_t instead of long xdiff: make xdfile_t.nrec a size_t instead of long xdiff: split xrecord_t.ha into line_hash and minimal_perfect_hash xdiff: use unambiguous types in xdl_hash_record() xdiff: use size_t for xrecord_t.size xdiff: make xrecord_t.ptr a uint8_t instead of char xdiff: use ptrdiff_t for dstart/dend doc: define unambiguous type mappings across C and Rust