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

git-subtree documentation fix request: split example causes fatal error

From
AKAlexander Krupp <obs@akr.yagii.de>
Date
Jul 9, 2025, 11:01 UTC
Message-ID
<6907e423-324f-459f-a62e-fe6be14f4f73@akr.yagii.de>

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
Read the documentation on git-subtree and try it:
 > git clone git://git.kernel.org/pub/scm/git/git.git test-git
Cloning into 'test-git'...
remote: Enumerating objects: 392367, done.
remote: Counting objects: 100% (7710/7710), done.
remote: Compressing objects: 100% (1126/1126), done.
remote: Total 392367 (delta 7015), reused 7002 (delta 6575), pack-reused 
384657
Receiving objects: 100% (392367/392367), 131.92 MiB | 49.57 MiB/s, done.
Resolving deltas: 100% (296075/296075), done.
 > cd test-git/
 > git subtree split --prefix=gitweb --annotate='(split) ' \
 >                      0a8f4f0^.. --onto=1130ef3 --rejoin \
 >                      --branch gitweb-latest
fatal: '0a8f4f0^..' does not refer to a commit
 >
What did you expect to happen? (Expected behavior)
Example should work as documented.
What happened instead? (Actual behavior)
see above.
What's different between what you expected and what actually happened?
Anything else you want to add:

Recommend a fix of the documentation. Due to lack of experience with subtree I cannot provide.

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info] git version: git version 2.43.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 6.4.0-150600.23.50-default #1 SMP PREEMPT_DYNAMIC Fri May  9 22:09:52 UTC 2025 (dee422c) x86_64 compiler info: gnuc: 7.5 libc info: glibc: 2.38 $SHELL (typically, interactive shell): /bin/bash

[Enabled Hooks]

Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)
Read the documentation on git-subtree and try it:
> git clone git://git.kernel.org/pub/scm/git/git.git test-git

Cloning into 'test-git'... remote: Enumerating objects: 392367, done. remote: Counting objects: 100% (7710/7710), done. remote: Compressing objects: 100% (1126/1126), done. remote: Total 392367 (delta 7015), reused 7002 (delta 6575), pack-reused 384657 Receiving objects: 100% (392367/392367), 131.92 MiB | 49.57 MiB/s, done. Resolving deltas: 100% (296075/296075), done.

> cd test-git/
> git subtree split --prefix=gitweb --annotate='(split) ' \
>                      0a8f4f0^.. --onto=1130ef3 --rejoin \
>                      --branch gitweb-latest
fatal: '0a8f4f0^..' does not refer to a commit
>
What did you expect to happen? (Expected behavior)
Example should work as documented.
What happened instead? (Actual behavior)
see above.
What's different between what you expected and what actually happened?
Anything else you want to add:
Recommend a fix of the documentation. Due to lack of experience with subtree I cannot provide.

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info] git version: git version 2.43.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 6.4.0-150600.23.50-default #1 SMP PREEMPT_DYNAMIC Fri May 9 22:09:52 UTC 2025 (dee422c) x86_64 compiler info: gnuc: 7.5 libc info: glibc: 2.38 $SHELL (typically, interactive shell): /bin/bash

[Enabled Hooks]
Next: Marc Branchaud
Message 1 of 2 in “git-subtree documentation fix request: split example causes fatal error”
  1. Alexander KruppJul 9, 2025
  2. Marc BranchaudJul 9, 2025

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.