From: Michael Lukashov <michael.lukashov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] fetch --all/--multiple: keep all the fetched branch information
Date: Wed, 24 Feb 2010 22:54:18 +0300 [thread overview]
Message-ID: <63cde7731002241154o40ad7e6eh26f20017f7854fc3@mail.gmail.com> (raw)
In-Reply-To: <7vpr3uqwya.fsf_-_@alter.siamese.dyndns.org>
Patch 3 does not apply correctly:
Applying: fetch --all/--multiple: keep all the fetched branch information
error: patch failed: t/t5521-pull-options.sh:72
error: t/t5521-pull-options.sh: patch does not apply
Patch failed at 0001 fetch --all/--multiple: keep all the fetched
branch information
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
On Wed, Feb 24, 2010 at 10:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Since "git fetch" learned "--all" and "--multiple" options, it has become
> tempting for users to say "git pull --all". Even though it may fetch from
> remotes that do not need to be fetched from for merging with the current
> branch, it is handy.
>
next prev parent reply other threads:[~2010-02-24 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 18:22 [PATCH 1/2] t5521: fix and modernize Junio C Hamano
2010-02-24 18:22 ` [PATCH 2/2] builtin-fetch --all/--multi: propagate options correctly Junio C Hamano
2010-02-24 19:02 ` [PATCH 3/3] fetch --all/--multiple: keep all the fetched branch information Junio C Hamano
2010-02-24 19:07 ` Teemu Likonen
2010-02-24 19:54 ` Michael Lukashov [this message]
2010-02-24 19:59 ` Junio C Hamano
2010-02-24 20:28 ` Michael Lukashov
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=63cde7731002241154o40ad7e6eh26f20017f7854fc3@mail.gmail.com \
--to=michael.lukashov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).