git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] docs: explain behaviour of remote add without tag option

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 4, 2015, 15:46 UTC
Message-ID
<54F728E7.5080600@drmicha.warpmail.net>
In-Reply-To
<1425424320-4091-2-git-send-email-me@ikke.info>
Kevin Daudt venit, vidit, dixit 04.03.2015 00:12:
Show 23 quoted lines
> 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>`
> 
So, how does this relate to:
http://permalink.gmane.org/gmane.comp.version-control.git/264592

I don't mind you taking this over at all, it's just that we should keep things together where the discussion begun.

Michael
Previous: Kevin DaudtNext: Kevin Daudt
Message 3 of 4 in “docs: explain behaviour with no tagopt set”
  1. 1/2 docs: explain behaviour with no tagopt setKevin Daudt, Mar 3, 2015
  2. 2/2 docs: explain behaviour of remote add without tag optionKevin Daudt, Mar 3, 2015
  3. Michael J GruberMar 4, 2015
  4. Kevin DaudtMar 4, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.