Git development
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Tony Luck <tony.luck@gmail.com>, git@vger.kernel.org
Subject: Re: git fetch --tags doesn't quite do what I expect
Date: Fri, 18 Nov 2005 14:04:58 -0800	[thread overview]
Message-ID: <20051118220458.GA5665@agluck-lia64.sc.intel.com> (raw)
In-Reply-To: <7v1x1diuuy.fsf@assigned-by-dhcp.cox.net>

On Fri, Nov 18, 2005 at 12:06:29PM -0800, Junio C Hamano wrote:
> I am not good at documenting things, so I'd appreciate if
> somebody paraphrased the above and send it back to me in a patch
> form to update the document ;-).


How about this:

[PATCH] Update pull/fetch --tags documentation

When fetching/pulling from a remote repository the "--tags" option
can be used to pull tags too.  Document that it will limit the pull
to only commits reachable from the tags.

Signed-off-by: Tony Luck <tony.luck@intel.com>

---

diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt
index 0e502ae..a25d04a 100644
--- a/Documentation/fetch-options.txt
+++ b/Documentation/fetch-options.txt
@@ -8,7 +8,9 @@
 -t, \--tags::
 	By default, the git core utilities will not fetch and store
 	tags under the same name as the remote repository;  ask it
-	to do so using `--tags`.
+	to do so using `--tags`.  Using this option will bound the
+	list of objects pulled to the remote tags.  Commits in branches
+	beyond the tags will be ignored.
 
 -u, \--update-head-ok::
 	By default `git-fetch` refuses to update the head which

      reply	other threads:[~2005-11-18 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 19:14 git fetch --tags doesn't quite do what I expect Tony Luck
2005-11-18 20:06 ` Junio C Hamano
2005-11-18 22:04   ` Luck, Tony [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=20051118220458.GA5665@agluck-lia64.sc.intel.com \
    --to=tony.luck@intel.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox