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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 15, 2007, 23:39 UTC
Message-ID
<7vfy1f8pmm.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200709152114.54985.elendil@planet.nl>
Frans Pop <elendil@planet.nl> writes:
Show 10 quoted lines
> 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.

Previous: Frans PopNext: Frans Pop
Message 2 of 3 in “Conflicting "-n" short options for git-pull?”
  1. Frans PopSep 15, 2007
  2. Junio C HamanoSep 15, 2007
  3. Frans PopSep 16, 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.