> -----Original Message-----
> From: fossil-users-boun...@lists.fossil-scm.org 
> [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf 
> Of Andy Bradford
> Sent: Thursday, October 02, 2014 1:15 PM
> To: Stephan Beal
> Cc: Fossil SCM user's discussion
> Subject: Re: [fossil-users] I have two trunks?
> 
> 
> Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200:
> 
> > The weird  thing is, he's  got two "initial  empty 
> commits". i'm  at a
> > loss to explain that.
> 
> Seems that one of  them must have been created with  an older 
> fossil and
> the  other  created with  a  newer  version  from Fossil's  
> trunk  which
> currently does  not force an  initial commit comment of  
> ``initial empty
> check-in'' when the fossil is created.
> 
> Would be  interesting to know  how the  repository was 
> created.  I don't
> know how Chiselapp imports a repository,  but is it possible 
> that the it
> might have created the additional trunk when it was uploaded?
> 
> Andy

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 tossed my local, and then cloned down the one on chisel.  (Have done
this in several places, actually.)

*  I later added a new branch successfully as expected off trunk (in this
case named 'sqlite3-3.8.6').  This is why I don't think the 'new trunk upon
upload' theory is true (assuming my recollection is correct)

*  Then today, as mentioned, I cloned afresh to a different machine (which
is why I disbelieve the 'fork because of out-of-sync repos' hypothesis), and
opened, and this is when I noticed I had the apparently empty root.  I did
not check the gui at this time, alas, I figured I was getting old.  So I
checked stuff into root that I was pretty darn sure was already there
(because if it wasn't it would have made creating all those other branches
painful, and I would have remembered that).

*  I take a look at the timeline on the gui, and Lo! And Behold! What
appears to be multiple trunks.

Anyway, again, not a crisis for me, but I didn't think this was possible in
the schema of things, and thought somebody might like to know if it is a
symptom of some sort of bug.

-dave


_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to