On 13 May 2013 23:42:46 -0600
Andy Bradford amb-fos...@bradfords.org wrote:
That is, it's backwards: you first do some work, then decide to
commit and decide this commit should start its own branch
rather than continuing the current one, so you create that
new branch while
On Tue, May 14, 2013 at 11:17 PM, Stephan Beal sgb...@googlemail.comwrote:
Poking around a little in the repo i just randomly selected a really old
version of checkin.c which does not contain the --branch option to the ci
command:
Hi,
I've been experimenting with fossil for some private projects of mine
and now want to use the 'branch' facility. According to the 'help'
text for 'branch', the syntax to create a new branch is:
fossil branch new BRANCH-NAME BASIS ?OPTIONS?
but it doesn't explain what BASIS is.
Looking
On Tue, May 14, 2013 at 01:55:56AM +, varro wrote:
I've been experimenting with fossil for some private projects of mine
and now want to use the 'branch' facility. According to the 'help'
text for 'branch', the syntax to create a new branch is:
fossil branch new BRANCH-NAME BASIS
Thus said Konstantin Khomoutov on Tue, 14 May 2013 07:40:41 +0400:
That is, it's backwards: you first do some work, then decide to commit
and decide this commit should start its own branch rather than
continuing the current one, so you create that new branch while
committing.
5 matches
Mail list logo