On Wed, Oct 6, 2010 at 8:33 AM, Luke Plant <l.plant...@cantab.net> wrote: > On Tue, 2010-10-05 at 22:29 +0100, I wrote: > >> Russell - beware - I think bitbucket has managed to create a very broken >> clone. I did a fork as well, and both of our repositories are missing >> thousands of commits. I can do a pull from django/django and I then get >> a complete repository which then seems to be compatible with >> django/django. I've e-mailed the bitbucket folks, but have left my >> clone as it is for now to allow them to work out what has gone wrong. > > It seems that the clones being created are not corrupted, but bitbucket > is choosing a 'forkpoint' which means that you get a partial repository. > You can get a full repository by pulling from django/django and pushing > back to your clone. It would be helpful if you did that on your clone > Russell - at the moment if I do 'hg outgoing freakboy' I get thousands > of commits that you are missing.
Done. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
