On 5/25/2011 7:29 AM, Gilles wrote:
> 1. Should the repository be located at the very top of the directory
> tree where files will be added and commited?
>
> For instance, if the files I'll be adding/committing live below C:\,
> should the repository be C:\myrepo, or is it OK to locate it anywhere
> on the hard drive, eg. D:\whatever\lmyrepo?

It doesn't matter what drive or folder you put the repo database in, 
except that you don't want to put it inside your working copy. E.g., if 
your project is in c:\myproj, the only place your repo shouldn't be is 
in c:\myproj. Also, you want to avoid storing the repo on a network 
drive most of the time.

> 2. Is it OK to have spaces in the path leading to the repo and the
> files, eg. C:\This is a directory\myrepo, and D:\This is where my
> files are\some file.txt?

Yeah, it's cool.

> 3. Is it possible _not_ to be prompted for a comment when committing a
> file? I'd just like to type "fossil commit", and be done with it.

Every commit has to have a comment, but you can specify it on the 
command line like this:

   fossil commit -m "my comment"

> 4. Is it possible to open the repository in a DOS box (C:\fossil.exe
> open c:\myrepo), and add/commit from a Windows application such as a
> text editor?
> When I tried this, I got this error: "C:\fossil.exe: not within an
> open checkout"

I don't really understand what you're trying to do there.

At the very beginning of a project, do something like this:

   fossil new c:\fossil-repos\myproj.fossil
   cd c:\myproj
   fossil open c:\fossil-repos\myproj.fossil

There is now a _FOSSIL_ file in c:\myproj and nothing else unless you 
had some files there already. (And it's ok if you did!) You won't need 
to do the above steps again until you start a new project (or a few 
other things, but relax for now). 'fossil open' is not a daily activity.

Now, say you have some work you want to commit. Assuming you're still in 
c:\myproj...

   fossil add .

to add all the not-yet-checked-in files here to your commit or...

   fossil add some-file some-other-file

Then...

   fossil status

Make sure that the output matches the branch you thought you were on and 
shows the files you thought you changed. (Not that fossil will ever be 
wrong about this, but that you might be.)

   fossil commit -m "Lovely work."

Wahoo!

So I have no idea what you mean about adding or committing from a test 
editor. If you have a text editor that will give you a command prompt 
inside it, then I would expect fossil to work fine so long as you first 
cd to the project directory.

-- 
Joshua Paine
LetterBlock: Web Applications Built With Joy
http://letterblock.com/
301-576-1920
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to