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 23:28:23 +0300 [thread overview]
Message-ID: <63cde7731002241228g5ef3154fw5b0c2858cbc168f@mail.gmail.com> (raw)
In-Reply-To: <7vy6iil81k.fsf@alter.siamese.dyndns.org>
Well, these patches solve the problem.
Thanks for your work!
On Wed, Feb 24, 2010 at 10:59 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Michael Lukashov <michael.lukashov@gmail.com> writes:
>
>> Patch 3 does not apply correctly:
>
> It probably has a trivial confict, because there is an added test to the
> second patch since I sent it out. Please add this after applying [2/3].
>
> diff --git a/t/t5521-pull-options.sh b/t/t5521-pull-options.sh
> index c18d829..84059d8 100755
> --- a/t/t5521-pull-options.sh
> +++ b/t/t5521-pull-options.sh
> @@ -51,4 +51,25 @@ test_expect_success 'git pull -q -v' '
> test -s err)
> '
>
> +test_expect_success 'git pull --force' '
> + mkdir clonedoldstyle &&
> + (cd clonedoldstyle && git init &&
> + cat >>.git/config <<-\EOF &&
> + [remote "one"]
> + url = ../parent
> + fetch = refs/heads/master:refs/heads/mirror
> + [remote "two"]
> + url = ../parent
> + fetch = refs/heads/master:refs/heads/origin
> + [branch "master"]
> + remote = two
> + merge = refs/heads/master
> + EOF
> + git pull two &&
> + test_commit A &&
> + git branch -f origin &&
> + git pull --all --force
> + )
> +'
> +
> test_done
>
prev parent reply other threads:[~2010-02-24 20:28 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
2010-02-24 19:59 ` Junio C Hamano
2010-02-24 20:28 ` Michael Lukashov [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=63cde7731002241228g5ef3154fw5b0c2858cbc168f@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).