git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Martin Nicolay <m.nicolay@osm-ag.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: missing tags from "git fetch"
Date: Wed, 2 Oct 2019 17:24:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1910021707570.32588@cpza.bfz-tzou.qr> (raw)
In-Reply-To: <20191002135518.GA3599@sigill.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

On Wednesday 2019-10-02 15:55, Jeff King wrote:
> So instead of this:
>
>> $ git fetch origin master
>
> try this:
>
>  $ git fetch origin

It creates the master branch. This is what I'm trying to avoid.

> or even this:
>
>  $ git fetch origin master:refs/remotes/origin/master

Bingo. It's ugly but it works. Problem solved :-).

> There's more discussion in this thread (but it looks like no patches
> ever came out of it):
>
>  https://public-inbox.org/git/20170817092853.hteuzni5lxia4ejf@sigill.intra.peff.net/

The explanation makes a kind of sense, but if someone want to avoid 
polluting the tags when fetching into FETCH_HEAD one could get it with 
--no-tags. So this is more of a misguided attempt to get a seemingly 
sensible default while destroying a consistent behaviour.

Sometimes I can see why people say git is confusing ;-).

Thanks
Martin Nicolay

-- 

No MS-Word attachments (http://www.gnu.org/philosophy/no-word-attachments.html)
_______________________________________________________________________________
OSM AG | Ruhrallee 191 | 45136 Essen | Fon: 0201-89 555 | Fax: 0201-89 55 400
web: www.osm-ag.de | e-mail: info@osm-ag.de
IBAN: DE67 4325 0030 0001 0059 82 | BIC: WELADED1HRN
USt-ldNr.: DE163337313 | HRB: 28171 Essen
Aufsichtsratsvorsitzende: Dipl.-Kff. Sabine Elsas
Vorstand: Johannes Kuhn (Vorsitzender), Christian Damsky, Axel Roland

--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.
_______________________________________________________________________________

  reply	other threads:[~2019-10-02 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 13:10 missing tags from "git fetch" Martin Nicolay
2019-10-02 13:55 ` Jeff King
2019-10-02 15:24   ` Martin Nicolay [this message]
2019-10-25 10:17   ` Martin Nicolay
2019-11-22 13:00     ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LSU.2.20.1910021707570.32588@cpza.bfz-tzou.qr \
    --to=m.nicolay@osm-ag.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).