Re: [fossil-users] fossil 1.34 segfault on git import

On Sun, Dec 27, 2015 at 10:23 PM, Richard Hipp wrote: > Still working on the ability to clone a Git repository - that feature > is not ready yet. I've seen your documentation changes with regarding to hierarchical manifests. Great think you specify first. > However, one side

Re: [fossil-users] fossil 1.34 segfault on git import

On Mon, Dec 28, 2015 at 12:12 PM, Karel Gardas wrote: > My final goal would be to have OpenBSD CVS mirrored > into fossil. It's a question if to use cvs->git->fossil transition > here especially when considering incremental imports or just write > some tool to do proper

Re: [fossil-users] fossil 1.34 segfault on git import

On Mon, Dec 28, 2015 at 12:58 PM, Karel Gardas wrote: > Baruch, thanks a lot for your references. Indeed, all three were > completely new to me. I googled somehow into different territory so > far it seems... You can also search this mailing list's history (

Re: [fossil-users] Show current checkout and branch in Web UI

On 12/27/15, Richard Hipp wrote: > My previous patch was not quite right. After a second look, I checked > in a slightly different fix. I won't be able to test the new fix on > windows until about this time tomorrow. > I can now confirm that the patch checked in yesterday

Re: [fossil-users] Show current checkout and branch in Web UI

Thanks, Richard! Since it seems you have some bandwidth available to play with Fossil, could you have a look‎ at those two rename bugs that cause grief too, in case these are quick fixes? The second one is more important. 1. (In May) Anofos reported that renaming a file on the branch and

Re: [fossil-users] fossil 1.34 segfault on git import

> I've seen your HEAD changes, I'm on 2dd25909da and the > space-effeciency is really nice to have. I'm not sure if this is > faster than in the past since I'm not testing on the same hardware > setup. I'll see if it crashes or not and if not, then I'll fire on the > original test server and test