Message info
To:Fossil SCM user\'s discussion From:Stephan Beal Subject:Re: [fossil-users] Thanks and some questions Date:Sun, 18 Mar 2012 17:24:04 +0100

On Sun, Mar 18, 2012 at 5:10 PM, <> wrote:
I notice the .fossil file is created in my home directory when using

It will create it wherever you tell it to. e.g.:

fossil new /tmp/foo.fossil
mkdir ~/foo
cd ~/foo
f open /tmp/foo.fossil

Then ~/foo is your checkout and the repo is /tmp/foo.fossil. The relationship is one-way: the checkout knows about the repo but not the other way around.

Because I am testing how fossil works to learn how to use it for my
workflows, I have created several fossil repos for different test projects
and then sometimes delete the whole subdirectory containing the repo when I
am done testing. Does this cause anything to be orphaned inside the .fossil
file in home directory? How do I to tell fossil to clean up this file and
let fossil know the repo(s) I was testing with have been deleted?

You don't need to do anything - the main fossil file doesn't know about the checkouts. Each checkout maintains a local _FOSSIL_ file which is another sqlite3 which holds metadata which is automatically generated from the main repo. It also holds your local stash, update undo, and such.
I often add programs to the project and I don't always remember to tell
fossil about them.

Don't worry - fossil never knew about them :).

What is the correct way to use fossil so when you work on
new projects where you don't have everything that will ultimately be part of
the project in your directory from the beginning? What should I be doing to
make sure fossil knows about all the new code? add doesn't seem to work, and
stat or chan doesn't flag newly created files that I haven't already

fossil add file
fossil commit -m 'foo' file

To see the list of "unmanaged" files:

fossil extra

Another question is on annotate. When I use annotate I see the change
history for a file. But if only one line of the file was changed repeatedly
it seems I don't see the change for each commit, only the last value. Is
this right and is there a way to show all the changes done to one file even
if it's all the same line, maybe with diffs from one commit to the next? I
would like to be able to quickly identify what I have done to a file all
throughout its history. Thanks to everyone!

This is how annotate works (it's not a bug). There currently is no feature to display ALL changes from ALL versions at one time (and i can't imagine how that would be readable).

----- stephan beal