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 <estifo...@gmail.com> 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"
>
> The fix in fossil would be to have a real branch selected on open if
> one is not specified. I.e. default to trunk but if trunk does not
> exist default to something that does.
>
> Hopefully my analysis is accurate :)
>
> On Sat, May 21, 2011 at 8:55 AM, Zed A. Shaw <zeds...@zedshaw.com> 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://dpaste.de/cY4y/
>>
>> I can put up with the stupid leaves behavior, but this is completely
>> unforgivable. There's no way in hell *anyone* should be able to get
>> fossil in a state that causes it to REMOVE ALL MY FILES.
>>
>> How do I fix this, and more importantly, how is it going to be prevented
>> in the future?
>>
>> And no, nobody on my project actually did this. There's no commit that
>> removes everything, and in fact fossil itself thinks the files are
>> missing after the update.
>>
>> --
>> Zed A. Shaw
>> http://zedshaw.com/
>> _______________________________________________
>> 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
