On 1/9/15 3:35 PM, Richard Boehme wrote:
Good evening. I have a small fossil repository that I've been
committing into for a couple of weeks now, and when I tried to commit
a bunch of files, it indicated the repository is corrupt.
Can anyone recommend how I can fix this?
I also have my
On 12/4/14, 5:09 AM, Richard Hipp wrote:
Should be working. Are you *sure* you typed the right password?
Yes -- I am sure. For good measure, I just tried it again. Both times I
copied and pasted the password
~ $ mkdir /tmp/f
~ $ fossil clone
On 2/26/13 1:12 PM, Stephan Beal wrote:
Brief comment from tablet (and no stackoverflow account) - managing
/etc with fossil is a poor idea because it does not support
permissions and some files in /etc are very sensitive to ownership and
perms. Fossil is not the right tool for that job.
i
On 01/12/2013 09:22 PM, John Found wrote:
If this is the case, I whould suggest better solution. Only 3..5 cases
in a year are not enough to train the team enough and to increase the
situation awareness of the people. Isn't it better to make fossil to
fork randomly with probability, let say,
On 01/12/2013 09:48 PM, John Found wrote:
I am not trolling. It is Reductio ad absurdum that proves D. Richard
Hipp is wrong in his statement. Solving technical problems by
high-handed methods is wrong by definition.
The source is available, so you should feel free to download and add in
I too have been saddened by the two flame wars on this list lately. I have held
onto the list because Fossil is super valuable to me and I want to stay in the
loop.
I can only hope that folks will learn to think before hitting reply in the new
year...
michael at barrow dot me
+1.408.782.4249
On 12/25/2012 12:44 AM, Michael Richter wrote:
This leaves me doubly confused. Neither of these command lines works
for me. There is no fossil cap I can see. (Fossil whines about
unknown command: cap.) And fossil new doesn't have that command
line that I can see. Is this some variant
I'm a faithful Fossil user and I have enjoyed its limitations compared
to Git because I consider them features. And pardon my commentary as I
typically lurk on the list rather than provide ongoing input to the
development.
If Git does all of this fancy stuff already, why not just use Git?
On 9/14/12 11:53 AM, Bill Burdick wrote:
Rest assured that even if weird features like rebasing were to
pollute Fossil, no one would force you to use them :)
But the size and complexity of the resulting application which is known
for being well-engineered could suffer...
--
michael at
On 8/15/12 12:21 PM, Nick Zalutskiy wrote:
Ideally I'd like to revert that commit somehow and do two smaller
commits thereafter. Since there is no rewriting history in fossil, I
assume that this would involve doing a new commit that is the
opposite of the incorrect one, and then replying the
Currently it looks to the first person to commit as though their
changes were discarded. The file is marked MERGED yet only contains
content from the last person to add. Perhaps not something that will
happen very often but the behavior is clearly wrong.
Unless I did something wrong
Firstly, I'm running:
This is fossil version 1.21 [002580c50d] 2011-12-13 13:53:56 UTC
Perhaps I'm confused, but the documentation for autosync being enabled says:
autosync If enabled, automatically pull prior to commit
or update and automatically push after
On 4/25/12 6:49 PM, Richard Hipp wrote:
What command did you use to create the tag?
fossil tag add foo current
I don't see any code associated with the tag command that will do an
autosync. My suspicious is that the documentation you site above is
incorrect and that tag creation should be
On 04/18/2012 10:35 AM, Miles Fidelman wrote:
I've been trying to build Fossil from source on a Debian Squeeze box.
Hey Miles -- long time, no see/hear. Hope you are well. Welcome to the
world of Fossil! I love this stuff.
Talk to you later,
Michael
--
Michael Barrow
michael at barrow
On Sat, 7 Jan 2012 17:20:03 -0500, sky5w...@gmail.com wrote:
Yes, I have been reading about the JSON work, but I prefer not to go
that route.
I'm confused. What would a csv output version offer that the JSON
currently does not?
--
Michael Barrow
michael at barrow dot me
+1 (408) 782-4249
15 matches
Mail list logo
