Fossil with Commonmark

Update of "Branching"
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Artifact ID: f4ecbbb4a4e9b1eade5248b6ac4b624e7a7692c3
Page Name:Branching
Date: 2008-10-19 13:06:27
Original User: eric
Next e30533ccc1986ee177295ac390e16d6b974e6ff6
Content

We probably need some notes on branching.

For now, here is a response to ticket [f90265fc83]:

# create testing branch
fossil tag branch testing uuid1

# where uuid1 is the point at which you want to branch
# Note that the above command creates a new checkin which is a
# sibling of uuid1 and identical to it.

# You still need to tell fossil to use it in the working directory
fossil update testing

# do some experimental work
...

# back to main branch
fossil update uuid1
fossil update

# The second update is needed because the main branch may have
# moved on from uuid1.

Note that fossil has no concept of a default branch, and in the presence of multiple forks and branches you are usually safer to give an explicit argument to fossil update.

Because fossil supports distributed operation, forks which are not deliberate branches can be quite common, and there is probably no safe algorithm for "the latest non-branch UUID".