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 ch
Hi all,
I appreciate the help offered in identifying what I was doing incorrectly.
Upon further investigation, I remembered why I added the original
`origin.fetch` parameter: I was compensating for shallow clones not fetching
all remote refs.
Here's the use case that I have:
[root@chabuduo
Alexander Huynh 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 pe
On Fri, Mar 08, 2019 at 12:40:15AM +0100, SZEDER Gábor wrote:
> On Thu, Mar 07, 2019 at 09:44:47PM +, Alexander Huynh wrote:
> > [git-test@chabuduo ~]$ cat > ~/.gitconfig
> > [remote "origin"]
> > fetch = +refs/heads/*:refs/remotes/origin/*
>
> Why do you do this?
>
> First,
On Thu, Mar 07, 2019 at 09:44:47PM +, Alexander Huynh wrote:
> Hello all,
>
> When running the latest release of git, I receive an error when attempting to
> fetch all remote branches from a repo:
>
> fatal: multiple updates for ref 'refs/remotes/origin/maint' not allowed
>
> The specifi
Hello all,
When running the latest release of git, I receive an error when attempting to
fetch all remote branches from a repo:
fatal: multiple updates for ref 'refs/remotes/origin/maint' not allowed
The specific ref that it fails on changes depending on the repository, but the
end result is
6 matches
Mail list logo
