From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: branch.pu.forcefetch
Date: Wed, 27 Dec 2006 22:20:36 +0100 [thread overview]
Message-ID: <emuntl$fn$2@sea.gmane.org> (raw)
In-Reply-To: 7vfyb159dn.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
>
>> For example, I clone the git repository anew, and I try to update it by
>> git-fetch a few days later. I get an error:
>>
>> * refs/remotes/origin/pu: not updating to non-fast forward branch 'pu'
>> of git://www.kernel.org/pub/scm/git/git
>
> Perhaps you would want something like this?
>
> if you are using separate remote layout:
>
> [remote "origin"]
> fetch = +refs/heads/pu:refs/remotes/origin/pu
> fetch = refs/heads/*:refs/remotes/origin/*
By the way, does the ordering matter here, i.e. does it matter if 'pu' fetch
line is before or after wildcards line?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-27 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 20:31 branch.pu.forcefetch Pavel Roskin
2006-12-27 21:14 ` branch.pu.forcefetch Jakub Narebski
2006-12-27 21:14 ` branch.pu.forcefetch Junio C Hamano
2006-12-27 21:20 ` Jakub Narebski [this message]
2006-12-28 21:29 ` branch.pu.forcefetch Pavel Roskin
2006-12-28 22:44 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 0:32 ` [PATCH 1/2] core.logallrefupdates: log remotes/ tracking branches Junio C Hamano
2006-12-29 0:32 ` [PATCH 2/2] Allow non-fast-forward of remote tracking branches in default clone Junio C Hamano
2006-12-29 4:35 ` Shawn Pearce
2006-12-29 16:39 ` Johannes Schindelin
2006-12-29 1:22 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 2:30 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 3:34 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 4:31 ` branch.pu.forcefetch Shawn Pearce
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='emuntl$fn$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).