From: Alexander Huynh <alex@grande.coffee>
To: Junio C Hamano <gitster@pobox.com>
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: Thu, 14 Mar 2019 17:20:32 +0000 [thread overview]
Message-ID: <20190314172032.GA10461@chabuduo> (raw)
In-Reply-To: <20190313234524.GA3053@chabuduo>
Hi all,
Sorry to bother one last time. After a bit more digging, I found that the
problem was with my workflow.
Shallow clones set `remote.origin.fetch` to one branch, so what I was doing in
the past was overriding the respository-specific `remote.origin.fetch` with my
global config.
I've now changed my workflow to perform a shallow clone at first, `cd` into
the repository, and locally set `remote.origin.fetch` to
`+refs/heads/*:refs/remotes/origin/*`.
Thanks again,
Alex
prev parent reply other threads:[~2019-03-14 17:20 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
2019-03-13 23:45 ` Alexander Huynh
2019-03-14 17:20 ` Alexander Huynh [this message]
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=20190314172032.GA10461@chabuduo \
--to=alex@grande.coffee \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.