On Fri, 13 Jun 2014, Richard Hipp wrote:
This appears to be working now on trunk. Get the latest code. Rerun
./configure and recompile (on a Linux system with FuseFS support -
Ubuntu 13.10 works for me after apt-get install fuse). Then:
fossil fusefs /tmp/myrepo
Then you can access
On 15.06.2014 15:45, Sergei Gavrikov wrote:
touch foo;f add foo;f ci -m add foo
touch foo-bar;f add foo-bar;f ci -m add foo-bar
mkdir bar;touch bar/.stick;f add --dotfiles bar;f ci -m add bar
mkdir bar-baz;touch bar-baz/.stick;f add --dotfiles bar-baz; f ci -m
add bar-baz
Now there are
On Sun, 15 Jun 2014, Thomas Schnurrenberger wrote:
I can reproduce this on lubuntu 14.04 LTS with Fossil compiled from trunk.
Thanks. Mine 10.04. More precision test case
% for i in a ab abc abcd;do touch $i; f add $i; f ci -m add $i; sleep 1; done
% for i in a ab abc abcd;do touch
On Sun, Jun 15, 2014 at 9:45 AM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
Thanks for nice Fossil FS! I found one strange thing. One my Fossil
repository has two directories, rootfs and rootfs-earth. After
fossil fuse mount `ls' could not find rootfs directory,
Should be fixed now.
The issue went away. Thanks!
Sergei
On Sun, 15 Jun 2014, Richard Hipp wrote:
On Sun, Jun 15, 2014 at 9:45 AM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
Thanks for nice Fossil FS! I found one strange thing. One my Fossil
repository has two directories, rootfs and rootfs-earth. After
I think you are wrong with your ideas. Committing not working code is not a bad
practice at all. Commit often, commit always. I am committing not working code
all the time and it works great for me. :)
I am only trying to keep the trunk branch working (notice: only trying).
Create new branch
Dear List,
I am hacking on a large, complicated code base in my spare time for fun.
I unzipped the tarball with many source files and imported it into a
Fossil repository. This aids me greatly in reviewing the code.
I often use the find . | xargs grep idiom (or some variant) to search
within
Well, maybe my ideas are wrong for you, but I assure you, to me they always
seem very right! :) Just like programming styles, mine *may* be very wrong to
many, but it's the best there is to me, and has never let me down!
But at least we agree on committing those work-in-progress files on some
* Joel Bruick j...@joelface.com [20140606 06:55]:
Richard Hipp wrote:
On Thu, Jun 5, 2014 at 8:33 PM, Nico Williams n...@cryptonector.com
mailto:n...@cryptonector.com wrote:
On Thu, Jun 5, 2014 at 7:22 PM, Matt Welland estifo...@gmail.com
mailto:estifo...@gmail.com wrote:
Cscope (+1) knows much more than just C.
On Jun 15, 2014 2:17 PM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
On Sun, 15 Jun 2014, Sean Woods wrote:
Dear List,
I am hacking on a large, complicated code base in my spare time for
fun. I unzipped the tarball with many source files
Thus said to...@acm.org on Mon, 16 Jun 2014 00:14:20 +0300:
OK, my problem is not so much with the committing act per se (of
non-working code,) -- besides, you do have to have a mechanism of
adding your changes, even WIP ones, in the repo -- it's with ending up
with a history /
11 matches
Mail list logo
