From: Ralf Thielow <ralf.thielow@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ralf Thielow via GitGitGadget <gitgitgadget@gmail.com>,
git <git@vger.kernel.org>,
Corentin BOMPARD <corentin.bompard@etu.univ-lyon1.fr>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] fetch.c: fix typo in a warning message
Date: Fri, 1 Nov 2019 10:48:44 +0100 [thread overview]
Message-ID: <CAN0XMOLDZo06Xa-Q9qVrVNk_J3+b2sP5e30f=_9s3nUw-B_JvQ@mail.gmail.com> (raw)
In-Reply-To: <20191031225310.GA211076@google.com>
Am Do., 31. Okt. 2019 um 23:53 Uhr schrieb Jonathan Nieder <jrnieder@gmail.com>:
>
> I wonder what this warning is trying to say. How would I go about
> triggering this message? The comment before says
>
> The relevant upstream is the fetched branch that is meant to
> be merged with the current one, i.e. the one fetched to
> FETCH_HEAD.
>
> So is this about when I'm fetching with a wildcard or something?
>
The message shows up when multiple refspecs/branches are passed,
like
$ git fetch --set-upstream origin master next
From https://github.com/git/git
* branch master -> FETCH_HEAD
* branch next -> FETCH_HEAD
warning: multiple branch detected, incompatible with --set-upstream
next prev parent reply other threads:[~2019-11-01 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 20:41 [PATCH 0/1] fetch.c: fix typo in a warning message Ralf Thielow via GitGitGadget
2019-10-31 20:41 ` [PATCH 1/1] " Ralf Thielow via GitGitGadget
2019-10-31 22:53 ` Jonathan Nieder
2019-11-01 9:48 ` Ralf Thielow [this message]
2019-11-02 5:50 ` Junio C Hamano
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='CAN0XMOLDZo06Xa-Q9qVrVNk_J3+b2sP5e30f=_9s3nUw-B_JvQ@mail.gmail.com' \
--to=ralf.thielow@gmail.com \
--cc=corentin.bompard@etu.univ-lyon1.fr \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=jrnieder@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 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).