On 10/2/2014 10:31 AM, Stephan Beal wrote:> The weird thing is, he's got two "initial empty commits". i'm at a loss
> to explain that.
> ....
> http://chiselapp.com/user/ziggurat29/repository/z29-3rdParty/timeline

I think I can partly explain the "two initial empty commits" part, or at least show off a similarly strange effect. I recently moved a private repository to Chiselapp so I could point at it from a series of blog posts. (Shameless plug: http://curiouser.cheshireeng.com/2014/09/11/wp-cli-utilities-source-code/ :-)

I had trouble with getting it to upload my repo directly, so I chose to let it create a fresh repo with the project code set to match mine, which is a feature chiselapp publicly offers.

The result is a timeline where there are two "initial empty commits", and amusingly since I haven't added anything to it since I published it, the second one is *after* all of the actual work. I suppose I should wonder what happens if a fresh clone is made...

http://chiselapp.com/user/rberteig/repository/WPCLI/timeline

I think this is an artifact of creating an empty repo, changing its project ID, and then syncing a bunch of older changes. I'm not sure if it is harmful or just confusing. Since it is now possible (IIRC) to create a repo without the initial empty commit, perhaps chiselapp should do that when it knows it is create a repo with a specific project ID.

And, actually, the clone experiment *is* more interesting than I expected. I just cloned from my WPCLI and opened it in an empty folder. The result is a folder containing only the _FOSSIL_ file. It opened [9f3230], aka the most recent checkin tagged "trunk", which is the second empty checkin.

I tried "fossil merge 3b301fad10" and it failed because there is no common ancestor. "fossil update 3b301fad10" works as expected.

One easy answer should be to move the extra initial checkin to the "mistake" branch and close it. However, attempting to do that reveals something else odd: the info page for the checkin shows the raw artifact and not the usual set of useful links including "edit".

https://chiselapp.com/user/rberteig/repository/WPCLI/info/9f323048ac

Is this a chiselapp bug or a fossil bug?

I don't know, but I'll likely poke at it a little more after lunch.

--
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

Reply via email to