Message info Subject:[fossil-users] Thanks and some questions Date:Sun, 18 Mar 2012 16:10:19 +0000 (GMT)

Hi I have been using Mercurial for my own small projects and am mostly
satisfied with it from a perspective of using it. I don't like that it uses
Perl scripts and other pieces to do what it does. I really like the fossil
and sqlite design having one standalone executable and no dependencies.
Outstanding! Big thanks to Dr. Richard and the devs for both sqlite and
fossil. I am moving towards using fossil for all my version control. All of
my development is either single developer or very small team.

I notice the .fossil file is created in my home directory when using
fossil. 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?

I often add programs to the project and I don't always remember to tell
fossil 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
added. This is a bit disturbing and I'm afraid new modules will go
untracked. I find myself using add * or addr. addr should usually be ok but
I don't like taking the chance to delete something. I realize unless you
shun nothing is actually lost but I don't know how it works and what
problems I could cause by addr. My question is really how should I be doing
this workflow.

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!

fossil-users mailing list