From: Nicolas Vilz 'niv' <niv@iaglans.de>
To: git@vger.kernel.org
Subject: Re: strange behavior when pulling updates / get uptodate with git.git
Date: Sat, 08 Apr 2006 23:19:10 +0200 [thread overview]
Message-ID: <443828CE.4070707@iaglans.de> (raw)
In-Reply-To: <7vmzeveqin.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Most likely it is aborted by the "pu" branch not
> fast-forwarding.
>
> Pull: +refs/heads/pu:refs/heads/pu
>
> or dropping "pu" altogether if you are not interested in it,
> would help.
Thank you, the +-sign helped me out.
Sincerly
Nicolas
prev parent reply other threads:[~2006-04-08 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 19:57 strange behavior when pulling updates / get uptodate with git.git Nicolas Vilz 'niv'
2006-04-08 20:55 ` Junio C Hamano
2006-04-08 21:19 ` Nicolas Vilz 'niv' [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=443828CE.4070707@iaglans.de \
--to=niv@iaglans.de \
--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).