Skip to content

Commit

Permalink
doc/fast-import: clarify how content states are built
Browse files Browse the repository at this point in the history
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
Signed-off-by: Jeff King <peff@peff.net>
  • Loading branch information
Eric S. Raymond authored and Jeff King committed Nov 8, 2012
1 parent 7e20105 commit e705288
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions Documentation/git-fast-import.txt
Original file line number Diff line number Diff line change
Expand Up @@ -442,7 +442,9 @@ their syntax.
^^^^^^
The `from` command is used to specify the commit to initialize
this branch from. This revision will be the first ancestor of the
new commit.
new commit. The state of the tree built at this commit will begin
with the state at the `from` commit, and be altered by the content
modifications in this commit.

Omitting the `from` command in the first commit of a new branch
will cause fast-import to create that commit with no ancestor. This
Expand Down Expand Up @@ -492,7 +494,9 @@ existing value of the branch.

`merge`
^^^^^^^
Includes one additional ancestor commit. If the `from` command is
Includes one additional ancestor commit. The additional ancestry
link does not change the way the tree state is built at this commit.
If the `from` command is
omitted when creating a new branch, the first `merge` commit will be
the first ancestor of the current commit, and the branch will start
out with no files. An unlimited number of `merge` commands per
Expand Down

0 comments on commit e705288

Please sign in to comment.