From: Pierre Habouzit <madcoder@debian.org>
To: Nicolas Pitre <nico@cam.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Jeff King <peff@peff.net>
Cc: Git ML <git@vger.kernel.org>
Subject: [bug in next ?] git-fetch/git-push issue
Date: Mon, 05 Nov 2007 18:56:54 +0100 [thread overview]
Message-ID: <20071105175654.GD6205@artemis.corp> (raw)
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
With the current tip of next[0], I have this bizare issue:
* I have two branches say master, and next, I'm on next.
* my master lags behind origin/master, but next is a fast-forward wrt
origin/next.
Now I git push:
┌─(18:16)──<~/some/repo next>──
└[artemis] git push
error: remote 'refs/heads/master' is not an ancestor of
local 'refs/heads/master'.
Maybe you are not up-to-date and need to pull first?
updating 'refs/heads/next'
from xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
to yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
Counting objects: 24, done.
Compressing objects: 100% (14/14), done.
Writing objects: 100% (14/14), done.
Total 14 (delta 12), reused 0 (delta 0)
refs/heads/next: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -> yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
updating local tracking ref 'refs/remotes/origin/master'
updating local tracking ref 'refs/remotes/origin/next'
And then I fetch, and here happens something really awkward:
┌─(18:17)──<~/some/repo next>──
└[artemis] git fetch
From ssh://some.host/some/repo.git
* [new branch] master -> origin/master
I believe there is something rotten in the kingdom of Denmark… though
my heads seems to always be OK, I think it's just an output issue.
The fun part is that if next has nothing to push, nothing happens:
┌─(18:55)──<~/dev/mmsx next>──
└[artemis] git push
error: remote 'refs/heads/master' is not an ancestor of
local 'refs/heads/master'.
Maybe you are not up-to-date and need to pull first?
error: failed to push to 'ssh://some.host/some/repo.git'
┌─(18:55)──<~/dev/mmsx next>──
└[artemis] git fetch && echo $?
0
[0] actually it's a bit farther than the current next, but for
parseopt thingies that are irrelevant here. My current origin/next
is 76374a65c41b80fa83f27b4dd924bd3967a07d69
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-11-05 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:56 Pierre Habouzit [this message]
2007-11-05 18:17 ` [bug in next ?] git-fetch/git-push issue Daniel Barkalow
2007-11-05 21:07 ` Jeff King
2007-11-05 21:41 ` Daniel Barkalow
2007-11-05 22:55 ` Jeff King
2007-11-05 23:22 ` Junio C Hamano
2007-11-05 23:59 ` Daniel Barkalow
2007-11-05 23:46 ` Daniel Barkalow
2007-11-06 3:26 ` Jeff King
2007-11-05 18:19 ` Pierre Habouzit
2007-11-06 17:56 ` Pierre Habouzit
2007-11-06 18:09 ` Jeff King
2007-11-06 18:23 ` Junio C Hamano
2007-11-06 18:41 ` Jeff King
2007-11-06 19:37 ` Pierre Habouzit
2007-11-07 15:11 ` Pierre Habouzit
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=20071105175654.GD6205@artemis.corp \
--to=madcoder@debian.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=peff@peff.net \
/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.