mirror of
https://github.com/martinvonz/jj.git
synced 2025-01-30 16:10:23 +00:00
docs: clarify that while named branches are not needed, they are supported
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:
parent
8f05007759
commit
ed3c95cde6
1 changed files with 6 additions and 5 deletions
|
@ -21,11 +21,12 @@ various use cases.
|
||||||
CLI for similar reasons. The index is very similar to an intermediate commit
|
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
|
between `HEAD` and the working copy, so workflows that depend on it can be
|
||||||
modeled using proper commits instead. [Details](#the-index).
|
modeled using proper commits instead. [Details](#the-index).
|
||||||
* **No need for branch names.** Git lets you check out a commit without
|
* **No need for branch names (but they are supported).** Git lets you check out
|
||||||
attaching a branch. It calls this state "detached HEAD". This is the normal
|
a commit without attaching a branch. It calls this state "detached HEAD". This
|
||||||
state in Jujutsu (there's actually no way -- yet, at least -- to have an
|
is the normal state in Jujutsu (there's actually no way -- yet, at least -- to
|
||||||
active branch). However, Jujutsu keeps track of all visible heads (leaves) of
|
have an active branch). However, Jujutsu keeps track of all visible heads
|
||||||
the commit graph, so the commits won't get lost or garbage-collected.
|
(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
|
* **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
|
branch', and new commits will automatically update the branch. This is
|
||||||
necessary in Git because Git might otherwise lose track of the new commits.
|
necessary in Git because Git might otherwise lose track of the new commits.
|
||||||
|
|
Loading…
Reference in a new issue