Hi, On Wed, Aug 13, 2008 at 04:04:51PM +0200, Thomas Schwinge wrote: > On Wed, Aug 13, 2008 at 08:54:40AM +0200, [EMAIL PROTECTED] > wrote:
> > The tricky part is that these changes were originally pushed to the > > github backup > > Someone please tell me and the others how to get access to that one? I myself just searched for "hurd" on github, and picked the right one among the results :-) To get commit access, you need to register at github, and get the owner of the repository (Madhusudan) to add you to it. > I can't seem to find an email or wiki page telling about this. Indeed there is none... Though I'm not sure this is a problem, considering that it was only meant as a temporary measure for the specific needs of GSoC? Now what about the promised Savannah backup? :-) > This is what happened, I think. flubber was down. Someone did a > commit for `community/scolobb.mdwn' in the web-interface. This change > was recorded in the web-interfaces's working copy, but obviously not > pushed to the flubber master copy, it being unreachable. In parallel, > someone did push a commit for `community/scolobb.mdwn' to the flubber > master copy, when it was available again. When doing that, this > change was automatically tried to be pushed to the web-interface's > working copy, creating a conflict in there. Apparently ikiwiki was > not able to resort to some sane state (how would it, nevertheless). Yeah, I understood it as well now that it's fixed again, and seeing that there were several web commits that didn't show up in the external repository before... I still wonder though what the purpose of this internal/external distinction is in the first place; and why there are no safeguards against such situations... -antrik-
