git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Daudt <me@ikke.info>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Kevin Daudt <me@ikke.info>
Subject: [PATCH 2/2] docs: explain behaviour of remote add without tag option
Date: Wed,  4 Mar 2015 00:12:00 +0100	[thread overview]
Message-ID: <1425424320-4091-2-git-send-email-me@ikke.info> (raw)
In-Reply-To: <1425424320-4091-1-git-send-email-me@ikke.info>

Only behaviour with these options are currently explained. Add
explanation what the default behaviour is.

Signed-off-by: Kevin Daudt <me@ikke.info>
---
 Documentation/git-remote.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index a77607b..5bde0e1 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -58,6 +58,9 @@ remote repository.
 With `--no-tags` option, `git fetch <name>` does not import tags from
 the remote repository.
 +
+With neither `--tags` or `--no-tags` set, imports only tags that are
+reachable from downloaded history.
++
 With `-t <branch>` option, instead of the default glob
 refspec for the remote to track all branches under
 the `refs/remotes/<name>/` namespace, a refspec to track only `<branch>`
-- 
2.3.0

  reply	other threads:[~2015-03-03 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 23:11 [PATCH 1/2] docs: explain behaviour with no tagopt set Kevin Daudt
2015-03-03 23:12 ` Kevin Daudt [this message]
2015-03-04 15:46   ` [PATCH 2/2] docs: explain behaviour of remote add without tag option Michael J Gruber
2015-03-04 16:47     ` Kevin Daudt

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=1425424320-4091-2-git-send-email-me@ikke.info \
    --to=me@ikke.info \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).