ok/jj
1
0
Fork 0
forked from mirrors/jj
Code Pull requests Activity

docs: clarify that while named branches are not needed, they are supported

Browse source 
The "No need for branch names" can be interpreted as implying that we
don't support named branches, which is of course not true. Try to
clarify it.
This commit is contained in:
Martin von Zweigbergk 2024-01-20 08:21:51 -08:00 committed by Martin von Zweigbergk
parent 8f05007759
commit ed3c95cde6
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/git-comparison.md
View file

@ -21,11 +21,12 @@ various use cases.
CLI for similar reasons. The index is very similar to an intermediate commit
between `HEAD` and the working copy, so workflows that depend on it can be
modeled using proper commits instead. [Details](#the-index).
* **No need for branch names.** Git lets you check out a commit without
attaching a branch. It calls this state "detached HEAD". This is the normal
state in Jujutsu (there's actually no way -- yet, at least -- to have an
active branch). However, Jujutsu keeps track of all visible heads (leaves) of
the commit graph, so the commits won't get lost or garbage-collected.
* **No need for branch names (but they are supported).** Git lets you check out
a commit without attaching a branch. It calls this state "detached HEAD". This
is the normal state in Jujutsu (there's actually no way -- yet, at least -- to
have an active branch). However, Jujutsu keeps track of all visible heads
(leaves) of the commit graph, so the commits won't get lost or
garbage-collected.
* **No current branch.** Git lets you check out a branch, making it the 'current
branch', and new commits will automatically update the branch. This is
necessary in Git because Git might otherwise lose track of the new commits.