On Tue, 20 Nov 2012 00:53:04 +0100, Themba Fletcher
<themba.fletc...@gmail.com> wrote:
On Mon, Nov 19, 2012 at 3:46 PM, Themba Fletcher
<themba.fletc...@gmail.com> wrote:
On Mon, Nov 19, 2012 at 3:12 PM, j. v. d. hoff
<veedeeh...@googlemail.com> wrote:
On Mon, 19 Nov 2012 22:49:22 +0100, Richard Hipp <d...@sqlite.org>
wrote:
On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff
<veedeeh...@googlemail.com>wrote:
hi there,
a modest suggestion:
<snip>
-- there seems no easy way to get a list of ignored files (as per the
`fsl set ignore-glob' setting.
in most cases I find that this setting should be part of the "global
state" of the project. in `hg'
there is a default file `.hgignore' where the glob patterns can be
put. I find this most useful since
in this way the ignore patterns can (but need not) be made part of the
project state that is transfered
to the "other" side.
This should help:
http://www.fossil-scm.org/index.html/doc/trunk/www/settings.wiki
Grrr. sorry for the rtfm -- I meant to add more here but hit send
instead....
At the very bottom of the page you'll find a general discussion about
versionable settings and specific reference to the
.fossil-settings/ignore-glob file, which is exactly what you're
looking for I believe.
thank you very much for this hint. I was not aware of this facility and,
yes, it's essentially what
I was looking for regarding making the ignore-glob settings an "intrinsic"
property of the project.
joerg
Themba
<snip>
I'd like to emphazise: this sure is not a complaint but just
expression of my opinion that the UI (and in turn adoption of
`fossil') might profit from some changes.
and I'd like to learn what the community thinks of these issues. are
all of them irrelavant?
Fossil was the first VCS that I used with any regularity. So, from
that point of view, I find when I'm working with bzr, git, and
particularly svn that they each seem really idiosyncratic and weird to
me. So there's *a* point of view, for what little it's worth.
I find fossil to be really scriptable, and over time I've either
scripted over the pain points, learned to accept them, or as often as
not learned to appreciate them. As a case in point, I too originally
found the chattiness of the autosync cycle to be kind of irritating.
Over time, however, I've found it provides a bit of peace of mind when
the network gets slow or something else happens (unexpectedly large
repo?) and I can clearly see that fossil's still doing or trying to do
something. Compare git, where you just type git clone and wait, never
knowing if you fat fingered the url or if you're slowly filling your
drive with 40G of nonsense...
Best regards,
Themba
j.
regards,
joerg
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
______________________________**_________________
fossil-users mailing list
fossil-users@lists.fossil-scm.**org
<fossil-users@lists.fossil-scm.org>
http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users>
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
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
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
