James, Oops, sorry I wasn't too clear. The repo is "private" in the sense that only a single user has ANY permissions at all (i.e., nobody, anonymous, developer, reader have no permissions at all). There are no private branches, and everything is in trunk (for this repo).
Bill, I tried naively adding '--verbose' to the options for clone, but fossil just complained about an unknown repository '--verbose'. Apparently not a correct option. I don't know fossil well enough for this either... :) Thanks, Tomek > Date: Thu, 23 Aug 2012 13:42:16 -0400 > From: [email protected] > To: [email protected] > Subject: Re: [fossil-users] Corrupt cloning of private repo > > On Thu, Aug 23, 2012 at 01:35:31PM -0400, Tomek Kott wrote: > > Bill, > > > > Nothing is shown in the timeline besides the "initial commit" entry, and no > > files are shown in the browser. Manually going to artifact pages also > > results in nothing. > > > > I also want to clarify that I am in no way trying to rush this: I have > > access to (two) full repos. I just want to diagnose the cloning process / > > private repo process for future use. > > > > Thanks, > > > > Tomek > > > > Is the branch private? Don't you need to pass --private while cloning? > > -- > James Turner > [email protected] > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
