Message info
 
To:Fossil SCM user\'s discussion From:Richard Hipp Subject:Re: [fossil-users] Thanks and some questions Date:Sun, 18 Mar 2012 12:43:10 -0400
 



On Sun, Mar 18, 2012 at 12:10 PM, <mailing@nym.mixmin.net> wrote:

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?

Orphan entries are created in the .fossil database. But they are small. And they are automatically cleaned up the next time you run the "fossil all" command.


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.

I think you want the "fossil extra" command to tell you what files are in your working folder that are not under management. And the "fossil addremove" command which will recursively descend through your working folder adding and removing files as necessary so that everything is under management again.


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?

The "fossil annotate" command is modeled after "cvs annotate", which only shows the most recent change for all current lines in the file. Can you show us an alternative display format that shows all historical changes to a file? What does hg do?

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



--
D. Richard Hipp
drh@sqlite.org