On Mon, Nov 03, 2014 at 08:41:24PM +0100, Stephan Beal wrote:
> In short, provide it a list of branch names and it returns the "tip" (most
> recent) version in each of those branches:
There is a table for the leaves, which likely is quitea bit faster.
Joerg
___
On Mon, Nov 3, 2014 at 8:41 PM, Stephan Beal wrote:
> while hacking on libfossil this evening i stumbled across a file i had
> stashed away and subsequently forgotten:
>
>
> http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/artifact/2bb2f4898b882cbb6a97ecc3e97ad356132dd6ad
>
It turns ou
Hi, all,
while hacking on libfossil this evening i stumbled across a file i had
stashed away and subsequently forgotten:
http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/artifact/2bb2f4898b882cbb6a97ecc3e97ad356132dd6ad
the SQL in that file was taking from an off-list exchange where li
On Mon, Nov 3, 2014 at 5:20 PM, Richard Hipp wrote:
>
> On Mon, Nov 3, 2014 at 10:48 AM, Stephan Beal
> wrote:
>
>> On Mon, Nov 3, 2014 at 3:06 PM, Taras Zakharko
>> wrote:
>>
>>> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
>>> Exception Codes: KERN_INVALID_ADDRESS at 0x00
On Mon, Nov 3, 2014 at 10:48 AM, Stephan Beal wrote:
> On Mon, Nov 3, 2014 at 3:06 PM, Taras Zakharko
> wrote:
>
>> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: KERN_INVALID_ADDRESS at 0x
>>
>
> @Richard: could this perhaps be related to the NULL sqli
On Mon, Nov 3, 2014 at 3:06 PM, Taras Zakharko
wrote:
> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x
>
@Richard: could this perhaps be related to the NULL sqlite3 pointer you
fixed last week?
--
- stephan beal
http://wa
> It shouldn't be crashing. But I don't have any idea what the problem is.
> Which version of Fossil are you running? Can you recompile using -g so
> that we get better information in the crash log?
This is the trunk [de17e35bf1] on OS X 10.10, using Apache/2.3.9
I am sure that the binary was
(I posted this initially to the "symlinks appear as regular files" thread,
reposting as new thread).
Someone reported to me that there are problems when a symlink is replaced
with a directory or vice versa. Here is the script that he generated to
illustrate the issue:
## Create repo and initial
On Mon, Nov 03, 2014 at 12:44:42PM +0100, Joerg Sonnenberger wrote:
> On Fri, Oct 31, 2014 at 03:08:25PM -0700, E. Timothy Uy wrote:
> > $ fossil export --git ../../../sqlite.fossil | git fast-import
> >
> > fatal: mark :60713 not declared
>
> I bet that is one of the timewarps. Those are current
On Mon, Nov 3, 2014 at 9:06 AM, Taras Zakharko
wrote:
> Dear all,
>
> I am hosting the Fossil repositories on our server via the CGI scripts (as
> described in fossil documentation). Every repository has its own CGI script
> (for cosmetic reasons).
>
> When creating a new repository and subsequen
Dear all,
I am hosting the Fossil repositories on our server via the CGI scripts (as
described in fossil documentation). Every repository has its own CGI script
(for cosmetic reasons).
When creating a new repository and subsequently trying to access it via CGI, I
get a crash in fossil. The re
On Fri, Oct 31, 2014 at 03:08:25PM -0700, E. Timothy Uy wrote:
> $ fossil export --git ../../../sqlite.fossil | git fast-import
>
> fatal: mark :60713 not declared
I bet that is one of the timewarps. Those are currently not handled in a
way git agrees with...
Joerg
__
12 matches
Mail list logo
