On Wed, 2011-12-21 at 12:25 -0500, Richard Hipp wrote:
> 
> On Wed, Dec 21, 2011 at 12:08 PM, Nick Zalutskiy <pace...@gmail.com>
> wrote:
>         I'm using fossil for the first time, on a new project -- it
>         hurts how
>         pragmatic and elegant fossil is, I had to try it. Over the
>         years, I've
>         developed some habits from hg and git that I can't seems to
>         reconcile
>         with how fossil does things. Can somebody tell me what I'm
>         missing or
>         how my workflow needs to adapt? I seem to be doing two steps
>         for tasks
>         that I preform dozens of times a day and that took one step in
>         both
>         git and hg.
>         
>         rm, mv:
>         
>         Managing files under source control in fossil is tedious,
>         since I have
>         to do every operation twice. One time for fossil and one time
>         for the
>         file system. Ex:
>         
>         $ fossil rm file1
>         DELETED file1
>         $ ls
>         file1
>         $ rm file1
>         
>         Is there a reason behind this design decision? 
> 
> Because that is the way CVS works.  And Fossil was written to replace
> CVS as the CM system for SQLite.
> 
> Oh, you mean a *good* reason for this behavior?  Then the answer is
> "no".
> 
> I fear to change it now, though, since it might really mess up people
> who are used to the older style.
> 
> 

Is this also why fossil (by default, anyways) ignores .dotfiles for
example on fossil add?

I've been using fossil daily for about six months, and it's my first
experience with any kind of version control system. The above behavior,
or more correctly the fact that I was not expecting it, caused me to get
quite superstitious about parts of my deployment workflow when in fact
the root cause was that I had not added the files to fossil that I
thought I had. Clearly my fault for missing it in the fine manual, but
you'll have that when you're learning a system :)

So if there are any changes on the roadmap with respect to how fossil
interacts with the filesystem I'd like to also advocate for changes to
"fossil add" and "fossil extra" to stop ignoring dotfiles. Maybe with a
default addition of ".*" to the ignore glob to maintain backwards
compatibility?

--
Themba Fletcher



_______________________________________________
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