I've noticed that if I remove a file from a working-set without
informing fossil about it, then fossil fails when I try to commit (other
changes in the set). That's fine, but it gives an obscure message:
fossil: no such file: somefile
fossil: SQLITE_BUSY: statement aborts at 2: [ROLLBACK]
Ron Wilson schrieb:
> On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa
> wrote:
>
>> On Sat, 21 May 2011 14:32:34 -0400
>> Richard Hipp wrote:
>>
>>> Does anybody have any other suggestions on how to prevent the lose
>>> of uncommitted work?
>>
>> Maybe not suggestion to prevent losing of
On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa wrote:
> On Sat, 21 May 2011 14:32:34 -0400
> Richard Hipp wrote:
>> Does anybody have any other suggestions on how to prevent the lose
>> of uncommitted work?
>
> Maybe not suggestion to prevent losing of uncommitted work, but I'm
> thinking a
On Sat, May 21, 2011 at 02:32:34PM -0400, Richard Hipp wrote:
> the "fossil revert" overwrote the undo stack. Maybe to prevent this, I
> should implement a multi-level undo? Does anybody have any other
> suggestions on how to prevent the lose of uncommitted work?
>
I've lost sometimes work with
On Sat, 21 May 2011 10:40:05 -0700
"Zed A. Shaw" wrote:
Hello Zed,
> Sorry, but I can't have this happen again. It already cost me 3 days
> of work and erased all my files. There's no way I'm going to use a
> VCS that erases all my files no matter how good it is.
>
> As much as I hate git, at
On Sat, 21 May 2011 14:32:34 -0400
Richard Hipp wrote:
> Bummer. I'm sorry you lost work.
I'm also sorry that Zed has lost work. :-(
> The bug that you hit had been there for ages - it wasn't new. But it
> was obscure. You were just the first to stumble over it. Sorry.
Despite of that, I'l
On Sat, May 21, 2011 at 11:13 AM, Zed A. Shaw wrote:
> On Sat, May 21, 2011 at 10:57:45AM -0700, Matt Welland wrote:
>> Hi Zed,
>>
>> Please confirm if you really lost local changes. That would be a big
>> concern for me. I haven't lost any non-checked in work and would like
>> to keep it that way
On Sat, May 21, 2011 at 2:15 PM, Zed A. Shaw wrote:
> On Sat, May 21, 2011 at 02:05:30PM -0400, Richard Hipp wrote:
> > On Sat, May 21, 2011 at 1:57 PM, Matt Welland
> wrote:
> >
> > > Hi Zed,
> > >
> > > Please confirm if you really lost local changes. That would be a big
> > > concern for me.
+1 for versionable settings, ignore-glob in particular!
BIll
On Sat, May 21, 2011 at 12:54 PM, Richard Hipp wrote:
>
>
> On Sat, May 21, 2011 at 1:29 PM, Ben Summers wrote:
>
>>
>> I had a quick look at supporting symlinks, but wasn't entirely sure the
>> best approach or where to start in t
On Sat, May 21, 2011 at 08:15:37PM +0200, Ramon Ribó wrote:
> Ambrose,
>
> I am not a troll.
>
> I was just remarking ironically that, although the poster has all the
> right to use whatever VCS he prefers and that he has all the right to
> inform all of us of his problems and preferences ma
On Sat, May 21, 2011 at 02:05:30PM -0400, Richard Hipp wrote:
> On Sat, May 21, 2011 at 1:57 PM, Matt Welland wrote:
>
> > Hi Zed,
> >
> > Please confirm if you really lost local changes. That would be a big
> > concern for me. I haven't lost any non-checked in work and would like
> > to keep it
Ambrose,
I am not a troll.
I was just remarking ironically that, although the poster has all the
right to use whatever VCS he prefers and that he has all the right to
inform all of us of his problems and preferences maybe he should
refrain on using this aggressive tone. Nobody likes to loose
On Sat, May 21, 2011 at 10:57:45AM -0700, Matt Welland wrote:
> Hi Zed,
>
> Please confirm if you really lost local changes. That would be a big
> concern for me. I haven't lost any non-checked in work and would like
> to keep it that way.
Oh it's confirmed.
--
Zed A. Shaw
http://zedshaw.com/
_
On Sat, May 21, 2011 at 01:46:49PM -0400, Richard Hipp wrote:
> > As much as I hate git, at least I know it'll keep working.
> >
>
> "fossil export | git fast-import" will get your stuff moved over
> efficiently. Thanks for hanging out with us. I expect you might come back
> to fossil someday, a
On Sat, May 21, 2011 at 07:44:40PM +0200, Ramon Ribó wrote:
> Do not worry Shaw, we shall manage to survive without you.
>
> err... how much did you contribute to the project?
I ton of new users and notoriety. I think without me pimping fossil and
writing about it you guys would still be used by
On Sat, May 21, 2011 at 1:57 PM, Matt Welland wrote:
> Hi Zed,
>
> Please confirm if you really lost local changes. That would be a big
> concern for me. I haven't lost any non-checked in work and would like
> to keep it that way.
>
I agree with Matt. I'm thinking you didn't really lose any wor
Hi Zed,
Please confirm if you really lost local changes. That would be a big
concern for me. I haven't lost any non-checked in work and would like
to keep it that way.
No tool is perfect and if there is a bug in fossil that causes local
changes to be inadvertently discarded we'd all like to know
On Sat, May 21, 2011 at 1:29 PM, Ben Summers wrote:
>
> I had a quick look at supporting symlinks, but wasn't entirely sure the
> best approach or where to start in the code.
>
Dmitry Chestnykh was working on this back in February. See
http://www.fossil-scm.org/fossil/timeline?r=symlinks for h
On Sun, May 22, 2011 at 1:44 AM, Ramon Ribó wrote:
> Do not worry Shaw, we shall manage to survive without you.
>
> err... how much did you contribute to the project?
>
>
While I shouldn't feed the troll, I can't help but point out Zed's blog
posts and peepcode video convinced me to give fossil a
On Sat, May 21, 2011 at 1:40 PM, Zed A. Shaw wrote:
> On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote:
> > Problem fixed in the latest fossil checkin.
>
> Sorry, but I can't have this happen again. It already cost me 3 days of
> work and erased all my files. There's no way I'm goin
Do not worry Shaw, we shall manage to survive without you.
err... how much did you contribute to the project?
RR
2011/5/21 Zed A. Shaw :
> On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote:
>> Problem fixed in the latest fossil checkin.
>
> Sorry, but I can't have this happen again.
On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote:
> Problem fixed in the latest fossil checkin.
Sorry, but I can't have this happen again. It already cost me 3 days of
work and erased all my files. There's no way I'm going to use a VCS
that erases all my files no matter how good it i
Hello,
I've been using fossil for a few repos, and I really like the system. I'm about
to move my final repo to it, but it's quite a big project and will require a
bit of work to fit in with fossil. In particular, it assumes the SCM supports
empty directories and symlinks. Also, in my current
On Sat, May 21, 2011 at 12:57 PM, Zed A. Shaw wrote:
> On Sat, May 21, 2011 at 12:46:56PM -0400, Richard Hipp wrote:
> > (1) "fossil undo" should restore all your files whenever something like
> this
> > happens.
> >
> > (2) I just checked in a change that prints a "panic" message if Fossil
> get
On Sat, May 21, 2011 at 12:46 PM, Richard Hipp wrote:
>
>
> On Sat, May 21, 2011 at 11:55 AM, Zed A. Shaw wrote:
>
>> I don't know what the hell has been changing lately, but this is really
>> starting to piss me off. First I get tons of leaves that won't go away
>> and that I have to constantl
On Sat, May 21, 2011 at 12:46:56PM -0400, Richard Hipp wrote:
> (1) "fossil undo" should restore all your files whenever something like this
> happens.
>
> (2) I just checked in a change that prints a "panic" message if Fossil gets
> into a state where it might want to delete all your files on an
On Sat, May 21, 2011 at 11:55 AM, Zed A. Shaw wrote:
> I don't know what the hell has been changing lately, but this is really
> starting to piss me off. First I get tons of leaves that won't go away
> and that I have to constantly close over and over, and *now* I'm getting
> this crap:
>
> http
On Sat, May 21, 2011 at 09:33:56AM -0700, Matt Welland wrote:
> One correction, you do have a "trunk" but fossil is not recognizing it:
>
> fossil branch
>
> /tmp/mongrel
> proxymustdie
> * ws-hybi-7
Yep, I see that now, but that doesn't explain why it would *REMOVE ALL
THE FI
One correction, you do have a "trunk" but fossil is not recognizing it:
fossil branch
/tmp/mongrel
proxymustdie
* ws-hybi-7
That looks like a fossil bug to me since "trunk" is not marked as
closed as far as I can tell.
On Sat, May 21, 2011 at 9:29 AM, Matt Welland wrote:
> Y
On Sat, May 21, 2011 at 09:29:33AM -0700, Matt Welland wrote:
> You have no trunk. I can reproduce what you saw by cloning mongrel,
> opening it, then doing the update. If you have no trunk you probably
> want to add the branch you want to your open "fossil open
> ../mongrel.fossil ws-hybi-7"
Ther
You have no trunk. I can reproduce what you saw by cloning mongrel,
opening it, then doing the update. If you have no trunk you probably
want to add the branch you want to your open "fossil open
../mongrel.fossil ws-hybi-7"
The fix in fossil would be to have a real branch selected on open if
one i
I don't know what the hell has been changing lately, but this is really
starting to piss me off. First I get tons of leaves that won't go away
and that I have to constantly close over and over, and *now* I'm getting
this crap:
http://dpaste.de/cY4y/
I can put up with the stupid leaves behavior,
32 matches
Mail list logo
