This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] gc --aggressive: make it really aggressive
- From: "J.C. Pizarro" <jcpiza at gmail dot com>
- To: "David Kastrup" <dak at gnu dot org>, "Johannes Schindelin" <Johannes dot Schindelin at gmx dot de>
- Cc: "Pierre Habouzit" <madcoder at debian dot org>, "Linus Torvalds" <torvalds at linux-foundation dot org>, "Daniel Berlin" <dberlin at dberlin dot org>, "David Miller" <davem at davemloft dot net>, ismail at pardus dot org dot tr, gcc at gcc dot gnu dot org, git at vger dot kernel dot org, gitster at pobox dot com
- Date: Thu, 6 Dec 2007 20:07:20 +0100
- Subject: Re: [PATCH] gc --aggressive: make it really aggressive
On 2007/12/06, David Kastrup <dak@gnu.org> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > However, I think that --aggressive should be aggressive, and if you
> > decide to run it on a machine which lacks the muscle to be aggressive,
> > well, you should have known better.
>
> That's a rather cheap shot. "you should have known better" than
> expecting to be able to use a documented command and option because the
> git developers happened to have a nicer machine...
>
> _How_ is one supposed to have known better?
>
> --
> David Kastrup, Kriemhildstr. 15, 44793 Bochum
In GIT, the --aggressive option doesn't make it aggressive.
In GCC, the -Wall option doesn't enable all warnings.
#
It's a "Tie one to one" with the similar reputations. #######
To have a rest in peace. #
#
J.C.Pizarro #