This is my favorite approach so far- simple, straightforward, and no
complications related to offline commits or someone forgetting to remove a
lock.
On Thu, Oct 20, 2011 at 2:07 PM, Mike Meyer m...@mired.org wrote:
On Thu, Oct 20, 2011 at 10:54 AM, Chris Peachment ch...@ononbb.comwrote:
I'm
I agree with the others, I usually start a branch as a part of the process
of working on some new feature. It just feels more organized than
remembering to decide what branch to use when I finally commit, or changing
the branch after the fact.
2011/8/9 Lluís Batlle i Rossell virik...@gmail.com
Is there a way to do in from the command line?
2011/8/9 Lluís Batlle i Rossell virik...@gmail.com
On Tue, Aug 09, 2011 at 01:01:55PM -0500, tpero...@compumation.com wrote:
So, how do you move commits in the trunk to a new branch after the fact.
Open the UI, click the checkin, then edit...
You sure jumped on that story fast!
I'm not Dr. Hipp, but since Fossil is based on a relational database while
UnQL is designed for non-relational databases, I doubt we'll see an UnQL
interface. Since UnQL is designed to mimic SQL, I'm not even sure what the
gain would be.
On Fri, Jul 29, 2011
When I switch between branches Fossil isn't removing files that belong to
the previous branch but not the current branch. Am I doing something wrong?
Example:
===
$ fossil new prj.fossil
project-id: 7e92eb48abd299ca1340a7bc0c86dba38097ad3e
server-id: 7efed910652f4fbceef4ec8cdcb152e7c944e7cc
.
To change branches it is not necessary to 'close' the workspace.
Just do
fossil update branchname
That will properly remove/add/update the files in the workspace.
Tomek
On Wed, Jul 13, 2011 at 2:55 PM, Brian Cottingham spiffyt...@gmail.com
mailto:spiffyt...@gmail.com wrote
, Richard Hipp d...@sqlite.org wrote:
On Wed, Jul 13, 2011 at 3:33 PM, Brian Cottingham spiffyt...@gmail.comwrote:
Should fossil close/open behave differently from fossil update? Is this a
bug in Fossil, or is it deliberate?
The behavior is deliberate. I'd understand what you are expecting from
there.
On Tue, Jun 28, 2011 at 8:34 AM, Brian Cottingham spiffyt...@gmail.com
wrote:
I'm using Fossil from a Cygwin terminal and I can't get the gdiff
command
to work with vimdiff. I've tried setting gdiff-command to vimdiff
but
running fossil gdiff I get 'vimdiff' is not recognized
I'm using Fossil from a Cygwin terminal and I can't get the gdiff command to
work with vimdiff. I've tried setting gdiff-command to vimdiff but running
fossil gdiff I get 'vimdiff' is not recognized as an internal or external
command. I tried setting the command to /usr/bin/vimdiff but I get The
9 matches
Mail list logo
