git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alexander Huynh <alex@grande.coffee>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG] fetching all remote branches results in failed multiple updates
Date: Fri, 08 Mar 2019 10:09:00 +0900	[thread overview]
Message-ID: <xmqqef7ikw9f.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190308000810.GA8044@chabuduo> (Alexander Huynh's message of "Fri, 8 Mar 2019 00:08:10 +0000")

Alexander Huynh <alex@grande.coffee> writes:

> Thanks for the clarification! One question: should we update the documentation
> at https://git-scm.com/docs/git-fetch#CRTB to not list this as an example to
> follow?

The example itself is valuable.  The way it is labeled might be
misleading to some people (although personally I do not find it
so).  It says "Typically such a variable may look like this" and
shows the fetch refspec that is given to a repository cloned from
anywhere by default.

I think it might help to update the text to clearly state that the
sample one is what you get in a clone without doing anything
special.  The example is primarily there to show you how each part
of the fetch refspec is used in the operations described in the
following paragraphs,and it is not there to tell you that you have
to add duplicate yourself to make these things described in the
following paragraphs to happen.


  reply	other threads:[~2019-03-08  1:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 21:44 [BUG] fetching all remote branches results in failed multiple updates Alexander Huynh
2019-03-07 23:40 ` SZEDER Gábor
2019-03-08  0:08   ` Alexander Huynh
2019-03-08  1:09     ` Junio C Hamano [this message]
2019-03-13 23:45       ` Alexander Huynh
2019-03-14 17:20         ` Alexander Huynh

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=xmqqef7ikw9f.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=alex@grande.coffee \
    --cc=git@vger.kernel.org \
    --cc=szeder.dev@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. 
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).