From: Daniel Johnson <computerdruid@gmail.com>
To: git@vger.kernel.org
Cc: Daniel Johnson <ComputerDruid@gmail.com>,
Tay Ray Chuan <rctay89@gmail.com>
Subject: [PATCH] Documentation: changes in the behavior of tagopt
Date: Fri, 6 Aug 2010 09:54:27 -0400 [thread overview]
Message-ID: <1281102867-6490-1-git-send-email-ComputerDruid@gmail.com> (raw)
In-Reply-To: <AANLkTikf96RLfTq4Q6DAPesr6j70CJfT8vBzidJk42dE@mail.gmail.com>
---
How does this look?
Documentation/config.txt | 4 +++-
Documentation/fetch-options.txt | 8 ++++++--
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index f81fb91..682ebef 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1627,7 +1627,9 @@ remote.<name>.tagopt::
Setting this value to \--no-tags disables automatic tag following when
fetching from remote <name>. Setting it to \--tags will fetch every
tag from remote <name>, even if they are not reachable from remote
- branch heads.
+ branch heads. Passing these flags directly to linkgit:git-fetch[1] can
+ override this setting. See options \--tags and \--no-tags of
+ linkgit:git-fetch[1].
remote.<name>.vcs::
Setting this to a value <vcs> will cause git to interact with
diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index 9333c42..2fdfeac 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt
@@ -49,7 +49,9 @@ ifndef::git-pull[]
endif::git-pull[]
By default, tags that point at objects that are downloaded
from the remote repository are fetched and stored locally.
- This option disables this automatic tag following.
+ This option disables this automatic tag following. The default
+ behavior for a remote may be specified with the remote.<name>.tagopt
+ setting. See linkgit:git-clone[1].
-t::
--tags::
@@ -58,7 +60,9 @@ endif::git-pull[]
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.
+ downloaded. The default behavior for a remote may be
+ specified with the remote.<name>.tagopt setting. See
+ linkgit:git-clone[1].
-u::
--update-head-ok::
--
1.7.2
next prev parent reply other threads:[~2010-08-06 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 18:56 [PATCH/RFC] fetch: allow command line --tags to override config Daniel Johnson
2010-08-05 9:56 ` Tay Ray Chuan
2010-08-06 13:54 ` Daniel Johnson [this message]
2010-08-08 2:17 ` [PATCH] Documentation: changes in the behavior of tagopt Tay Ray Chuan
2010-08-11 22:57 ` [RFC/PATCHv2] fetch: allow command line --tags to override config Daniel Johnson
2010-08-13 1:22 ` Junio C Hamano
2010-08-13 20:13 ` [RFC/PATCH] t5525: test the tagopt variable and that it can be overridden Daniel Johnson
2010-08-13 20:55 ` Ævar Arnfjörð Bjarmason
2010-08-13 21:27 ` [RFC/PATCHv2] " Daniel Johnson
2010-08-13 21:39 ` Ævar Arnfjörð Bjarmason
2010-08-14 21:32 ` Daniel Johnson
2010-08-14 21:37 ` Ævar Arnfjörð Bjarmason
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=1281102867-6490-1-git-send-email-ComputerDruid@gmail.com \
--to=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.com \
/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.