{"thread":{"id":"11162","subject":"Re: [PATCH] gc --aggressive: make it really aggressive","startedAt":"2007-12-06T19:07:20Z","lastAt":"2007-12-06T19:07:20Z","messageCount":1,"participants":["J.C. Pizarro"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"62182","messageId":"998d0e4a0712061107r47f99599m262ffc7aefc4938a@mail.gmail.com","threadId":"11162","inReplyTo":null,"subject":"Re: [PATCH] gc --aggressive: make it really aggressive","fromName":"J.C. Pizarro","fromEmail":"jcpiza@gmail.com","sentAt":"2007-12-06T19:07:20Z","receivedAt":"2007-12-06T19:07:20Z","isPatch":true,"sender":{"key":"jcpiza@gmail.com","avatar":null},"body":"On 2007/12/06, David Kastrup <dak@gnu.org> wrote:\n> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n>\n> > However, I think that --aggressive should be aggressive, and if you\n> > decide to run it on a machine which lacks the muscle to be aggressive,\n> > well, you should have known better.\n>\n> That's a rather cheap shot.  \"you should have known better\" than\n> expecting to be able to use a documented command and option because the\n> git developers happened to have a nicer machine...\n>\n> _How_ is one supposed to have known better?\n>\n> --\n> David Kastrup, Kriemhildstr. 15, 44793 Bochum\n\nIn GIT, the --aggressive option doesn't make it aggressive.\nIn GCC, the -Wall option doesn't enable all warnings.\n\n                                                           #\nIt's a \"Tie one to one\" with the similar reputations.   #######\n                             To have a rest in peace.      #\n                                                           #\n   J.C.Pizarro                                             #\n"}]}