From: Luck, Tony Date: Fri, 18 Nov 2005 22:04:58 GMT Subject: Re: git fetch --tags doesn't quite do what I expect Message-ID: <20051118220458.GA5665@agluck-lia64.sc.intel.com> 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 --- 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