the problem wasn't isolated to the repo (there were many problems) but suffice to say lack of shared issue tracking was a key point of failure and inability to discreetly version changesets created more suffering than good
On Mon, Nov 25, 2013 at 3:20 PM, Josh Soref <jso...@blackberry.com> wrote: > Lindsey Simon wrote: > > It seems like a shared repo is just a recipe for the troubles of the last > > shared repo. > > For those of us who didn't live through the last shared repo, is there a > document describing what happened? > > There's a great writeup from some Github using group who accidentally > force pushed over a few hundred repositories :). > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > >
