All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: branch.pu.forcefetch
Date: Wed, 27 Dec 2006 13:14:44 -0800	[thread overview]
Message-ID: <7vfyb159dn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1167251519.2247.10.camel@dv> (Pavel Roskin's message of "Wed, 27 Dec 2006 15:31:59 -0500")

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/*

Or traditional layout:

[remote "origin"]
	fetch = refs/heads/master:refs/heads/origin
	fetch = refs/heads/next:refs/heads/next
	fetch = refs/heads/maint:refs/heads/maint
	fetch = +refs/heads/pu:refs/remotes/pu

  parent reply	other threads:[~2006-12-27 21:14 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 ` Junio C Hamano [this message]
2006-12-27 21:20   ` branch.pu.forcefetch Jakub Narebski
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=7vfyb159dn.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.