From: Timo Schmiade <timo.schmiade@gmx.de>
To: git@vger.kernel.org
Subject: Strange behaviour of --tags when adding remotes
Date: Sat, 16 Apr 2011 12:50:17 +0200 [thread overview]
Message-ID: <20110416105017.GA2887@Discworld> (raw)
Hi all,
I just stumbled upon what I think is a bit of a strange behaviour when
using "git remote add" with the --tags option. The remote I added was
fetch'able after the command (it was added to .git/config), but there
was no remote tracking branch set up for it (i.e. the
.git/refs/remotes/<shortname> directory didn't exist).
Only after removing the "tagopt = --tags" option from .git/config was it
that "git fetch <shortname>" created a remote tracking branch for the
remote.
After double-checking the "man git-fetch", I still think this behaviour
is quite confusing, so I wanted to inform you about this.
Kind regards,
Timo
reply other threads:[~2011-04-16 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110416105017.GA2887@Discworld \
--to=timo.schmiade@gmx.de \
--cc=git@vger.kernel.org \
/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).