From: Junio C Hamano <gitster@pobox.com>
To: Frans Pop <elendil@planet.nl>
Cc: git@vger.kernel.org
Subject: Re: Conflicting "-n" short options for git-pull?
Date: Sat, 15 Sep 2007 16:39:45 -0700 [thread overview]
Message-ID: <7vfy1f8pmm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200709152114.54985.elendil@planet.nl> (Frans Pop's message of "Sat, 15 Sep 2007 21:14:54 +0200")
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.
next prev parent reply other threads:[~2007-09-15 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 19:14 Conflicting "-n" short options for git-pull? Frans Pop
2007-09-15 23:39 ` Junio C Hamano [this message]
2007-09-16 11:17 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vfy1f8pmm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=elendil@planet.nl \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox