{"thread":{"id":"25308","subject":"Implementation bug with cherry-picking multiple commits","startedAt":"2010-10-01T16:16:27Z","lastAt":"2010-10-01T16:16:27Z","messageCount":1,"participants":["Dun Peal"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"152243","messageId":"AANLkTimhwomGnmCEAyPaGj=fST8zkMO1sTyJ2dxRzWMW@mail.gmail.com","threadId":"25308","inReplyTo":null,"subject":"Implementation bug with cherry-picking multiple commits","fromName":"Dun Peal","fromEmail":"dunpealer@gmail.com","sentAt":"2010-10-01T16:16:27Z","receivedAt":"2010-10-01T16:16:27Z","isPatch":false,"sender":{"key":"dunpealer@gmail.com","avatar":"https://gravatar.com/avatar/42f3e6a1166eb44e33f24c20ccbe809fa8591413f366dfe3755c8a8d4935ace9?d=mp&s=160"},"body":"I tried using the new feature allowing the cherry-picking of multiple\ncommits at the same time:\n\n  $ git cherry-pick foo~100...foo\n\nI got an error that indicates a potential implementation bug:\n\n  error: cannot fork() for commit: Cannot allocate memory\n\nThis is a powerful CentOS server with almost 8GB of free RAM at the\ncherry-pick operation runtime.\n\nThanks, D\n"}]}