Conflicting "-n" short options for git-pull?

Conflicting "-n" short options for git-pull?

[Frans Pop]

Hello,

According to the man page for git-pull from git-core 1.5.3.1 (Debian 
package), two options are defined as having the short option "-n":

     -n, --no-summary
         Do not show diffstat at the end of the merge.
[...]
     -n, --no-tags
         By default, git-fetch fetches tags that point at objects that are
         downloaded from the remote repository and stores them locally. This
         option disables this automatic tag following.

Cheers,
Frans Pop

Re: Conflicting "-n" short options for git-pull?

[Junio C Hamano]

Frans Pop <elendil@planet.nl> writes:

> According to the man page for git-pull from git-core 1.5.3.1 (Debian 
> package), two options are defined as having the short option "-n":
>
>      -n, --no-summary
>          Do not show diffstat at the end of the merge.
> [...]
>      -n, --no-tags
>          By default, git-fetch fetches tags that point at objects that are
>          downloaded from the remote repository and stores them locally. This
>          option disables this automatic tag following.

The manpage option descriptions are shared between the
commands.  Maybe we should drop mention of the shorthand form.

When git-fetch is used -n means --no-tags because there is no
other -n; when git-pull indirectly invokes git-fetch, you need
to spell it --no-tags because --no-summary takes precedence.

Re: Conflicting "-n" short options for git-pull?

[Frans Pop]

On Sunday 16 September 2007, Junio C Hamano wrote:
> Frans Pop <elendil@planet.nl> writes:
> > According to the man page for git-pull from git-core 1.5.3.1 (Debian
> > package), two options are defined as having the short option "-n":
> >
> >      -n, --no-summary
> >          Do not show diffstat at the end of the merge.
> > [...]
> >      -n, --no-tags
> >          By default, git-fetch fetches tags that point at objects that
> > are downloaded from the remote repository and stores them locally. This
> > option disables this automatic tag following.
>
> The manpage option descriptions are shared between the
> commands.  Maybe we should drop mention of the shorthand form.

Not sure if that last is the correct solution. Wouldn't it mean that short 
options would not be documented at all anymore?

> When git-fetch is used -n means --no-tags because there is no
> other -n; when git-pull indirectly invokes git-fetch, you need
> to spell it --no-tags because --no-summary takes precedence.

That does explain, but it is not at all obvious from the documentation.
Guess this is a general "problem" in git then.


Another question.
Is it possible to set default options for commands somehow?
I'd like to run git-pull with '--no-summary' by default. I could of course 
define an alias, but that only covers 'git-pull' and not 'git pull'.
Does git itself have some mechanism for this?

Thanks,
Frans Pop