threads / discuss / 10990

git --prune --aggresive

Subject: git --prune --aggresive

## tl;dr

3 messages between Nov 23, 2007 and Nov 23, 2007.

replies: 2people: 2as markdown or json

Jakub Narebski· Nov 23, 2007, 09:58 UTC · lore

2396:[gitweb/web@git]# git gc --aggresive --prune usage: git-gc [--prune] [--aggressive] 2397:[gitweb/web@git]# git gc --prune --aggresive usage: git-gc [--prune] [--aggressive] 2398:[gitweb/web@git]# git --version git version 1.5.3.5

Either usage string should be fixed, as it suggests that you can specify both --aggresive and --prune, or git-gc should.

-- 
Jakub Narebski
Poland

Jakub Narebski· Nov 23, 2007, 10:08 UTC · re: Jakub Narebski · lore

Re: git --prune --aggresive

Jakub Narebski wrote:

Show 9 quoted lines

> 2396:[gitweb/web@git]# git gc --aggresive --prune
> usage: git-gc [--prune] [--aggressive]
> 2397:[gitweb/web@git]# git gc --prune --aggresive
> usage: git-gc [--prune] [--aggressive]
> 2398:[gitweb/web@git]# git --version
> git version 1.5.3.5
> 
> Either usage string should be fixed, as it suggests that you can specify 
> both --aggresive and --prune, or git-gc should.

I'm very sorry, my mistake: --aggresive instead of --aggressive. Please disregard this message...

-- 
Jakub Narebski
Poland

Matthieu Moy· Nov 23, 2007, 11:15 UTC · re: Jakub Narebski · lore

Re: git --prune --aggresive

Jakub Narebski <jnareb@gmail.com> writes:

Show 14 quoted lines

> Jakub Narebski wrote:
>
>> 2396:[gitweb/web@git]# git gc --aggresive --prune
>> usage: git-gc [--prune] [--aggressive]
>> 2397:[gitweb/web@git]# git gc --prune --aggresive
>> usage: git-gc [--prune] [--aggressive]
>> 2398:[gitweb/web@git]# git --version
>> git version 1.5.3.5
>> 
>> Either usage string should be fixed, as it suggests that you can specify 
>> both --aggresive and --prune, or git-gc should.
>
> I'm very sorry, my mistake: --aggresive instead of --aggressive.
> Please disregard this message...

Now, for the cool thing: with the latest git, I get the following.

$ git gc --aggresive --prune error: unknown option `aggresive' <----- this is what you wanted. usage: git-gc [options]

    --prune               prune unreferenced objects
    --aggressive          be more thorough (increased runtime)
    --auto                enable auto-gc mode

$ _

Thanks, parse_options.[ch]!

-- 
Matthieu