Re: [fossil-users] Windows newb questions
On Tue, 25 Jun 2013 14:36:52 -0700, Pete Rihaczek prihac...@gmail.com wrote: I think it serves its basic purpose of getting people up and running, but of course you'll run into more questions soon after that. It might be good for example to clarify that it's not necessary to actually close a repository. Also, my first instinct was to try to convert my .gitignore file to a fossil equivalent. I wanted to do that per project, so I had to dig to find out how to do that (and that you can only do it from the command prompt). Then when I did a test commit, I got the hint about how to avoid having to type --no-warnings, but I had to discover for myself that the only variant of the crnl-glob command that works on Windows requires the asterisk to be in single quotes, i.e. fossil settings crnl-glob '*' --global. That might be a nice additional hint for Windows users. Your document does what it claims to do, so whether you want to add a couple of extra hints based on my newbie experience is entirely optional of course. I don't have write access to the wiki, and have no experience with Git so I'll have to leave that someone in the know to write the 5mn guide to move from Git to Fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Tue, 25 Jun 2013 14:36:52 -0700, Pete Rihaczek prihac...@gmail.com wrote: Then when I did a test commit, I got the hint about how to avoid having to type --no-warnings, but I had to discover for myself that the only variant of the crnl-glob command that works on Windows requires the asterisk to be in single quotes, i.e. fossil settings crnl-glob '*' --global. I just ran that test on an XP host, but Windows seems happy with double-quotes: [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) [C:\]fossil.exe settings --global crnl-glob * [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
I can't speak to XP, but on my Win7 64-bit machine, only single quotes works. If I use double quotes, fossil comes back with a usage prompt. On Thu, Jun 27, 2013 at 5:30 AM, Gilles gilles.gana...@free.fr wrote: On Tue, 25 Jun 2013 14:36:52 -0700, Pete Rihaczek prihac...@gmail.com wrote: Then when I did a test commit, I got the hint about how to avoid having to type --no-warnings, but I had to discover for myself that the only variant of the crnl-glob command that works on Windows requires the asterisk to be in single quotes, i.e. fossil settings crnl-glob '*' --global. I just ran that test on an XP host, but Windows seems happy with double-quotes: [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) [C:\]fossil.exe settings --global crnl-glob * [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
c:\myrepo\fossil settings crnl-glob '*' -- OK on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 But in my case, the report is: crnl-glob(local) '*'-- Why local instead of global? And why is the * surrounded with '*' ? On Thu, Jun 27, 2013 at 8:30 AM, Gilles gilles.gana...@free.fr wrote: On Tue, 25 Jun 2013 14:36:52 -0700, Pete Rihaczek prihac...@gmail.com wrote: Then when I did a test commit, I got the hint about how to avoid having to type --no-warnings, but I had to discover for myself that the only variant of the crnl-glob command that works on Windows requires the asterisk to be in single quotes, i.e. fossil settings crnl-glob '*' --global. I just ran that test on an XP host, but Windows seems happy with double-quotes: [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) [C:\]fossil.exe settings --global crnl-glob * [C:\]fossil.exe settings access-log allow-symlinks auto-captcha auto-hyperlink auto-shun autosync binary-glob clearsign case-sensitive crnl-glob(global) * (snip) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Thu, Jun 27, 2013 at 6:45 PM, sky5w...@gmail.com wrote: c:\myrepo\fossil settings crnl-glob '*' -- OK on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 Can you please also try: c:\myrepo\fossil settings crnl-glob \* :-? But in my case, the report is: crnl-glob(local) '*'-- Why local instead of global? And why is the * surrounded with '*' ? See my response to Pete (just before this one). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Still don't understand the context of local vs global in this case? On Thu, Jun 27, 2013 at 2:13 PM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Jun 27, 2013 at 6:45 PM, sky5w...@gmail.com wrote: c:\myrepo\fossil settings crnl-glob '*' -- OK on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 c:\myrepo\fossil settings crnl-glob * -- FAIL on Windows 7 Can you please also try: c:\myrepo\fossil settings crnl-glob \* :-? But in my case, the report is: crnl-glob(local) '*'-- Why local instead of global? And why is the * surrounded with '*' ? See my response to Pete (just before this one). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Weird. i'd have to see what value fossil actually gets from your shell there to understand that one. Still don't understand the context of local vs global in this case? fossil settings are local (repo-specific) by default unless you use the --global flag (which isn't shown in the short-form help but probably should be ... it's in the trunk now). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
Ah, I didn't catch that --global switch as it was at the very bottom of the ui settings page. :( On Thu, Jun 27, 2013 at 2:34 PM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Weird. i'd have to see what value fossil actually gets from your shell there to understand that one. Still don't understand the context of local vs global in this case? fossil settings are local (repo-specific) by default unless you use the --global flag (which isn't shown in the short-form help but probably should be ... it's in the trunk now). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Or you can simply type fossil ui and in the browser go to Admin - Settings. There you can edit it. Or you can create a file .fossil-settings/crnl-glob - containing only a single character '*' - with your favorite editor and commit it. Then everyone else who checks out your repository can benefit from it too. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
Sorry, but I am still thwarted? c:\myrepofossil settings --global crnl-glob '*' c:\myrepofossil settings ~... case-sensitive (local) 0 crnl-glob(local) '*' This is fossil version 1.25 [4452f85156] 2013-05-28 21:31:57 UTC On Thu, Jun 27, 2013 at 3:16 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Or you can simply type fossil ui and in the browser go to Admin - Settings. There you can edit it. Or you can create a file .fossil-settings/crnl-glob - containing only a single character '*' - with your favorite editor and commit it. Then everyone else who checks out your repository can benefit from it too. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
I had no trouble on Win7 with fossil settings crnl-glob '*' --global Pete On Thu, Jun 27, 2013 at 2:08 PM, sky5w...@gmail.com wrote: Sorry, but I am still thwarted? c:\myrepofossil settings --global crnl-glob '*' c:\myrepofossil settings ~... case-sensitive (local) 0 crnl-glob(local) '*' This is fossil version 1.25 [4452f85156] 2013-05-28 21:31:57 UTC On Thu, Jun 27, 2013 at 3:16 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Or you can simply type fossil ui and in the browser go to Admin - Settings. There you can edit it. Or you can create a file .fossil-settings/crnl-glob - containing only a single character '*' - with your favorite editor and commit it. Then everyone else who checks out your repository can benefit from it too. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
If a local and a global setting exist, local have priority. Try: fossil unset crnl-glob Then you will see the '(global)' (Sory typing on my phone) -- Martin G. -Original Message- From: sky5w...@gmail.com To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Sent: jeu., 27 juin 2013 17:08 Subject: Re: [fossil-users] Windows newb questions Sorry, but I am still thwarted? c:\myrepofossil settings --global crnl-glob '*' c:\myrepofossil settings ~... case-sensitive (local) 0 crnl-glob(local) '*' This is fossil version 1.25 [4452f85156] 2013-05-28 21:31:57 UTC On Thu, Jun 27, 2013 at 3:16 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Or you can simply type fossil ui and in the browser go to Admin - Settings. There you can edit it. Or you can create a file .fossil-settings/crnl-glob - containing only a single character '*' - with your favorite editor and commit it. Then everyone else who checks out your repository can benefit from it too. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
Haha, well done. I love this mail list! On Thu, Jun 27, 2013 at 8:41 PM, Martin Gagnon eme...@gmail.com wrote: If a local and a global setting exist, local have priority. Try: fossil unset crnl-glob Then you will see the '(global)' (Sory typing on my phone) -- Martin G. -Original Message- From: sky5w...@gmail.com To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Sent: jeu., 27 juin 2013 17:08 Subject: Re: [fossil-users] Windows newb questions Sorry, but I am still thwarted? c:\myrepofossil settings --global crnl-glob '*' c:\myrepofossil settings ~... case-sensitive (local) 0 crnl-glob(local) '*' This is fossil version 1.25 [4452f85156] 2013-05-28 21:31:57 UTC On Thu, Jun 27, 2013 at 3:16 PM, Jan Nijtmans jan.nijtm...@gmail.com wrote: On Thu, Jun 27, 2013 at 8:18 PM, sky5w...@gmail.com wrote: c:\myrepofossil settings crnl-glob \* Usage: fossil settings ?PROPERTY? ?VALUE? Or you can simply type fossil ui and in the browser go to Admin - Settings. There you can edit it. Or you can create a file .fossil-settings/crnl-glob - containing only a single character '*' - with your favorite editor and commit it. Then everyone else who checks out your repository can benefit from it too. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Mon, 17 Jun 2013 16:47:39 -0700, Pete Rihaczek prihac...@gmail.com wrote: I confess that the up and running in 5 minutes tutorial took me considerably longer since I'm on Windows and had to work a few things out that weren't crystal clear. Perhaps incorporating some lessons learned into the 5 minute intro might save other Windows users some time. I wrote that wiki entry, and happen to use Fossil on Windows. Where did you struggle? Note that, as indicated, it's meant to get a single user up and running fast with the most basic commands, not for using Fossil for group development. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
Hi Gilles, I think it serves its basic purpose of getting people up and running, but of course you'll run into more questions soon after that. It might be good for example to clarify that it's not necessary to actually close a repository. Also, my first instinct was to try to convert my .gitignore file to a fossil equivalent. I wanted to do that per project, so I had to dig to find out how to do that (and that you can only do it from the command prompt). Then when I did a test commit, I got the hint about how to avoid having to type --no-warnings, but I had to discover for myself that the only variant of the crnl-glob command that works on Windows requires the asterisk to be in single quotes, i.e. fossil settings crnl-glob '*' --global. That might be a nice additional hint for Windows users. Your document does what it claims to do, so whether you want to add a couple of extra hints based on my newbie experience is entirely optional of course. Pete On Tue, Jun 25, 2013 at 1:29 PM, Gilles gilles.gana...@free.fr wrote: On Mon, 17 Jun 2013 16:47:39 -0700, Pete Rihaczek prihac...@gmail.com wrote: I confess that the up and running in 5 minutes tutorial took me considerably longer since I'm on Windows and had to work a few things out that weren't crystal clear. Perhaps incorporating some lessons learned into the 5 minute intro might save other Windows users some time. I wrote that wiki entry, and happen to use Fossil on Windows. Where did you struggle? Note that, as indicated, it's meant to get a single user up and running fast with the most basic commands, not for using Fossil for group development. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Windows newb questions
Greetings All, We're looking at using Fossil due to its support for ticketing (among other things), and I'm the designated point man to figure it all out and teach the rest of the lazy SOBs -- I mean developer team -- how it all works. :) Looks like a very nice bit of work, from what I've seen so far. ;) I confess that the up and running in 5 minutes tutorial took me considerably longer since I'm on Windows and had to work a few things out that weren't crystal clear. Perhaps incorporating some lessons learned into the 5 minute intro might save other Windows users some time. First thing I wanted to was convert the .gitignore file I use with Visual Studio to Fossil's format. This is a typical one: https://github.com/github/gitignore/blob/master/VisualStudio.gitignore Since I don't think glob format includes a comment symbol, I just ran things together like so: *.suo *.user *.sln.docstates */[Bb]in/ */[Oo]bj/ *_i.c *_p.c *.ilk etc. That seems to work even without putting trailing asterisks on folders, e.g. */[Bb]in/*. Then you run into Windows quirks, such as the fact that you can't create a folder starting with a . from within the Explorer GUI, so creating a .fossil-settings folder at the project root and then a .ignore-glob file in that has to be done via the command line. So far so good. But then I decided I wanted to globally set crnl-glob to * to avoid having to type --no-warnings at every check-in, but following what I could find online only resulted in Fossil telling me I was being a knucklehead by repeatedly responding with the usage hint. It turns out that an asterisk in single quotes does the trick on Windows, i.e. fossil settings crnl-glob '*' --global. FWIW. Some questions: 1) Coming from using Mercurial and Git, I'm using to firing up Visual Studio and getting to work without any source control prep. If the Fossil repository isn't open at the root of my project (i.e. no _FOSSIL_ file) and I then open it to commit changes I made while it was closed, it will first prompt to overwrite the changed files. That makes sense, and I can decline the overwrites and then commit, but it would seem that the desired workflow would be to open the repository before starting to work. I even found a blog entry that claims Fossil doesn't like it if you don't do that. Is there any threat beyond perhaps accidentally overwriting work? Related to that, is it necessary to close the repository when you're done, or is it OK to leave it open between sessions, reboots, etc.? I just want to make sure I understand the workflow to recommend and why. 2) I played with cloning a repository locally on the same drive, and autosync worked as expected. But of course I don't want to host the master repository for a project on my local drive, lest the drive fail. What would be the preferred method for sharing multiple repositories using a shared Windows fileserver? Simply throwing the files on a shared drive doesn't seem right due to locking and contention issues(?). Would the preferred method be creating the Windows service to share a number of .fossil repositories, and then people can clone and autosync to the various URLs presented by the service? Thank you, Pete ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
On Mon, Jun 17, 2013 at 7:47 PM, Pete Rihaczek prihac...@gmail.com wrote: Some questions: 1) Coming from using Mercurial and Git, I'm using to firing up Visual Studio and getting to work without any source control prep. Help me to understand: Are you starting a new project? If you are starting to work on an existing project, where did you get the files to work on if you didn't do the source control prep first? If the Fossil repository isn't open at the root of my project (i.e. no _FOSSIL_ file) and I then open it to commit changes I made while it was closed, it will first prompt to overwrite the changed files. That makes sense, and I can decline the overwrites and then commit, but it would seem that the desired workflow would be to open the repository before starting to work. I even found a blog entry that claims Fossil doesn't like it if you don't do that. Is there any threat beyond perhaps accidentally overwriting work? If you want to start the source control prep after the fact, that fine. The only danger is file overwriting. Note also the --keep option to fossil open which avoids all file overwriting. But if you make changes to some version of code you got out of band and then try to check it into fossil - are you sure you are checking it into the right branch? Are you sure nobody else has changed it in the meantime. There are lots of reasons not to do it that way. Just open the checkout from fossil first, then start editing, and you will avoid lots of potential problems and complications. Related to that, is it necessary to close the repository when you're done, or is it OK to leave it open between sessions, reboots, etc.? I just want to make sure I understand the workflow to recommend and why. Leave sessions open. There is hardly ever a good reason to close them. Sitting here typing this, I cannot think of even one reason why you would ever want to run fossil close. (You will notice, btw, that fossil close is not on the list of commonly used commands that appear when you type fossil help. ) 2) I played with cloning a repository locally on the same drive, and autosync worked as expected. But of course I don't want to host the master repository for a project on my local drive, lest the drive fail. What would be the preferred method for sharing multiple repositories using a shared Windows fileserver? Simply throwing the files on a shared drive doesn't seem right due to locking and contention issues(?). A shared drive will work, in theory, assuming file locking works on the shared drive. (Network filesystems are notoriously buggy in that respect.) Performance won't be optimal, but will probably be good enough. Would the preferred method be creating the Windows service to share a number of .fossil repositories, and then people can clone and autosync to the various URLs presented by the service? Thank you, My opinion of the preferred solution is to run Fossil from CGI on a Linux box. I'm guessing you aren't going to go for that solution, so my second choice would be to run Fossil as a windows service someplace. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Windows newb questions
Hi Richard, Help me to understand: Are you starting a new project? If you are starting to work on an existing project, where did you get the files to work on if you didn't do the source control prep first? In order to test Fossil, I essentially did the following: 1) created a folder for repositories (c:\fossil\repositories), and used fossil new to create a repo called test.fossil 2) went to the root of an existing Visual Studio project, and did a fossil open c:\fossil\repositories\test.fossil, saw the _FOSSIL_ file was created and 3) did fossil add . to add the existing files to the new repository At that point I saw all the debug detritus going into the repo, so I played with deleting and ignoring things. :) So anyway, that initial prep for an existing project has to be done with Git etc. as well. However at that point I wasn't sure if I have to prep each working session by opening the repo, working/committing, and then closing at the end. This guy http://ronperrella.blogspot.com/2012/12/fossil-first-steps.html says Fossil doesn't like it if the repository isn't open, and while he also mentions that there's little reason to close a repo, there's also little reason to think he must know what he's talking about since that information isn't on the official site, hence the question. If you want to start the source control prep after the fact, that fine. The only danger is file overwriting. Note also the --keep option to fossil open which avoids all file overwriting. That fully answers the question, thanks. But if you make changes to some version of code you got out of band and then try to check it into fossil - are you sure you are checking it into the right branch? Are you sure nobody else has changed it in the meantime. There are lots of reasons not to do it that way. Just open the checkout from fossil first, then start editing, and you will avoid lots of potential problems and complications. Related to that, is it necessary to close the repository when you're done, or is it OK to leave it open between sessions, reboots, etc.? I just want to make sure I understand the workflow to recommend and why. Leave sessions open. There is hardly ever a good reason to close them. Sitting here typing this, I cannot think of even one reason why you would ever want to run fossil close. (You will notice, btw, that fossil close is not on the list of commonly used commands that appear when you type fossil help. ) This is also good information, since it's not clear from a newbie perspective. A shared drive will work, in theory, assuming file locking works on the shared drive. (Network filesystems are notoriously buggy in that respect.) Performance won't be optimal, but will probably be good enough. Hmm. I would hate to rely on Windows then if there's a reasonable possibility of corruption that way. Would the preferred method be creating the Windows service to share a number of .fossil repositories, and then people can clone and autosync to the various URLs presented by the service? Thank you, My opinion of the preferred solution is to run Fossil from CGI on a Linux box. I'm guessing you aren't going to go for that solution, so my second choice would be to run Fossil as a windows service someplace. I'd be happy to do a Linux box if I had the option, but I probably don't. So it sounds like in a pure-Microsoft environment, the windows service option is preferred. Thanks again, Pete ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
