All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Rico Secada <coolzone@it.dk>,
	Mathias Lafeldt <misfire@debugon.org>
Subject: [PATCH] pull: Remove --tags option from manpage
Date: Wed, 03 Nov 2010 21:55:48 +0100	[thread overview]
Message-ID: <4CD1CC54.1060905@web.de> (raw)
In-Reply-To: <7vhbgdlxof.fsf@alter.siamese.dyndns.org>

"Fetch all tags and merge them" does not make any sense as a request at
the logical level, even though it might be more convenient to type.

Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
---

Am 22.10.2010 23:33, schrieb Junio C Hamano:
> Mathias Lafeldt <misfire@debugon.org> writes:
>> From git-pull's manpage:
>>
>> -t
>> --tags
>>         Most of the tags are fetched automatically as branch
>>         heads are downloaded, but tags that do not point at
>>         objects reachable from the branch heads that are being
>>         tracked will not be fetched by this mechanism.  This
>>         flag lets all tags and their associated objects be
>>         downloaded. [...]
> 
> Can somebody submit a patch to stop this part of "fetch-options.txt" from
> getting included in "git pull" manpage please, by the way?

Maybe something like this?


 Documentation/fetch-options.txt |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index 470ac31..5ce1e72 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt
@@ -53,6 +53,7 @@ endif::git-pull[]
 	behavior for a remote may be specified with the remote.<name>.tagopt
 	setting. See linkgit:git-config[1].

+ifndef::git-pull[]
 -t::
 --tags::
 	Most of the tags are fetched automatically as branch
@@ -63,6 +64,7 @@ endif::git-pull[]
 	downloaded. The default behavior for a remote may be
 	specified with the remote.<name>.tagopt setting. See
 	linkgit:git-config[1].
+endif::git-pull[]

 -u::
 --update-head-ok::
-- 
1.7.3.2.213.g5fe186

      reply	other threads:[~2010-11-03 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  3:37 Git pull doesn't get the tags Rico Secada
2010-10-22  9:04 ` Mathias Lafeldt
2010-10-22 12:23   ` Rico Secada
2010-10-22 22:25     ` Junio C Hamano
2010-10-23 16:34       ` Rico Secada
2010-10-22 21:33   ` Junio C Hamano
2010-11-03 20:55     ` Jens Lehmann [this message]

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=4CD1CC54.1060905@web.de \
    --to=jens.lehmann@web.de \
    --cc=coolzone@it.dk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=misfire@debugon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.