I've uploaded some scripts for fossil to the following URL:
http://www.serice.net/fossil-scripts/
If there are more direct ways of doing these things, please let me
know. The scripts are described below in alphabetical order:
1) fossil-branch []
- If a commit is not specified, show
> __FOSSIL__ is required, though you can rename it to ".fos" if you
> don't want to look at it.
This is dangerous because the following commands do very bad things:
fossil extras --dotfiles
fossil clean -f --dotfiles
T
is just *.tar, one corrupt byte will cause
you to lose at most up to the start of the next file in the archive.
What's the story with SQLite? What's my exposure to a single corrupt
byte?
Thank You,
Paul Serice
___
fossil-user
On Sun, 2010-01-24 at 18:29 -0500, D. Richard Hipp wrote:
> On Jan 24, 2010, at 5:42 PM, Paul Serice wrote:
> > Just search for "Berkeley DB usage leading to respository
> > corruption and data loss" on the Wikipedia page for Subversion.
>
> That's why sub
fossil tag --raw add closed
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
f of the CPU on a virtual machine that is a
> 1/20th slice of a real server. ... How much more efficient does that
> need to be?
Lots ... if it's CGI under Windows.
Thank You,
Paul Serice
___
fossil-users mailing list
fossil-users@li
6 matches
Mail list logo