git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gc --aggressive: make it really aggressive

From
JPJ.C. Pizarro <jcpiza@gmail.com>
Date
Dec 6, 2007, 19:07 UTC
Message-ID
<998d0e4a0712061107r47f99599m262ffc7aefc4938a@mail.gmail.com>
On 2007/12/06, David Kastrup <dak@gnu.org> wrote:
Show 14 quoted lines
> 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                                             #
Message 1 of 1 in “Re: [PATCH] gc --aggressive: make it really aggressive”
  1. J.C. PizarroDec 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.