I have the same issue with one of my repo and I used bisect to
pinpoint it to this commit:
http://fossil-scm.org/index.html/info/bc8d368b66053450c7f323b4e479fb5b4a878684
I don't know how the git export works though, so no idea how to fix this.
___
On Wed, Jan 25, 2012 at 12:16:51PM +0100, Antoine Chavasse wrote:
I have the same issue with one of my repo and I used bisect to
pinpoint it to this commit:
http://fossil-scm.org/index.html/info/bc8d368b66053450c7f323b4e479fb5b4a878684
I don't know how the git export works though, so no
On Wed, Jan 25, 2012 at 12:28 PM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
I'm running with this on very large repositories. Did you do rebuilds
after that?
Yes, I did a rebuild on my test repo after building each revision.
There have been a number of bugs in the manifest parser
On Wed, Jan 25, 2012 at 3:25 PM, Antoine Chavasse a.chava...@gmail.comwrote:
Ok, I have found what the problem with that particular repo is: it's
something I started on git and back when I imported it to fossil it
generated some broken manifests where some branch that had been
created at some
Hi all,
I've just noticed that there's link 'Check-ins' in the View Ticket
page. Clicking on this I can see page 'Checkins Associated With Ticket
xxx' which in my case is empty. Looks like this is somewhat related to
a thing I was discussing some time ago
2012/1/25 Jacek Cała jacek.c...@gmail.com
Now the question: how can I associate a check-in with a ticket?
Write the name of the ticket (or any reasonably prefix thereof) inside
[...] in the check-in comment.
--
D. Richard Hipp
d...@sqlite.org
___
6 matches
Mail list logo
