From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: nightly tarballs of git
Date: Sat, 16 Sep 2006 20:04:13 +0200 [thread overview]
Message-ID: <eehe9n$v1b$1@sea.gmane.org> (raw)
In-Reply-To: 20060916175853.GA24124@redhat.com
Dave Jones wrote:
> * refs/heads/pu: does not fast forward to branch 'pu' of
> git://git.kernel.org/pub/scm/git/git;
> not updating.
> Something wicked happend.
Did you put '+' before 'pu' line in 'origin' file in remotes?
It should read
Pull:+refs/heads/pu:refs/heads/pu
Alternatively you can give --force option to git-fetch.
See
http://git.or.cz/gitwiki/GitFaq#head-a1f9a3e511e0b866d788d7cb600637a9b976a994
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-16 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060914172754.GF8013@us.ibm.com>
2006-09-14 17:51 ` nightly tarballs of git Dave Jones
2006-09-14 19:15 ` Junio C Hamano
2006-09-14 19:36 ` Dave Jones
2006-09-14 19:48 ` Jakub Narebski
2006-09-14 20:06 ` Junio C Hamano
2006-09-16 17:58 ` Dave Jones
2006-09-16 18:04 ` Jakub Narebski [this message]
2006-09-16 18:09 ` Junio C Hamano
2006-09-17 0:03 ` Dave Jones
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='eehe9n$v1b$1@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).