Bingo.
On 10/2/2014 11:33 AM, dave wrote:
....
I'm tending to suspect not (additional trunk at creation) for a reason that
I will soon make clear, but the 'version mismatch' hypothesis is
interesting. Fyi, the creation process went like this:
* I created my repo locally, with current (v1.29, June 12th) fossil binary.
I added a few things to trunk, and made some branches and added a bunch of
stuff there. I decided to put it on a third party hosting site so I could
avoid hosting myself.
* Its big, so chisel can't import it, but they have a feature where you
explicitly supply the project id, and then you can sync your big repo into
it. So I did that.
I'm currently running a hair older fossil than you, but very similar
vintage and likely newer than the one on chiselapp. "version 1.29
[77f53423ae]"
I followed essentially the same path, except my repo was small enough
that it should have allowed the upload but failed. I wonder if a version
mismatch was part of that story?
It certainly could be. Chiselapp's shows "Fossil version [3d49f04587]
2014-01-27 17:33:44" as the title text for the link back to
fossil-scm.org in the page footer in their default skin. Going by the
date alone, it is *older*.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
