From: Jacob Helwig <jacob.helwig@gmail.com>
To: "bkorb@gnu.org" <bkorb@gnu.org>
Cc: GIT <git@vger.kernel.org>
Subject: Re: failed to push
Date: Mon, 1 Mar 2010 13:27:03 -0800 [thread overview]
Message-ID: <2793902788222999372@unknownmsgid> (raw)
In-Reply-To: <4B8C2E68.3020507@gnu.org>
On Mar 1, 2010, at 13:15, Bruce Korb <bkorb@gnu.org> wrote:
> Hi,
>
> This message has no meaning at all. I know it failed to push.
> I can tell from the comment "[rejected]". It would be nice
> to know *WHY* it was rejected so I can fix the problem.
> How do I determine the cause, please? Thank you!! Regards, Bruce
>
> $ git push
> To ssh://bkorb@autogen.git.sourceforge.net/gitroot/autogen/autogen
> ! [rejected] master -> master (non-fast forward)
> error: failed to push some refs to 'ssh://bkorb@autogen.git.sourceforge.net
> /gitroot/autogen/autogen'
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
It tells you right there at the end of the rejected line. The push
would have resulted in a non-fast-forward update of the branch.
To "fix" this, you need the current commit pointed to by the branch as
one of the ancestors of the commits you're trying to push.
prev parent reply other threads:[~2010-03-01 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 21:15 failed to push Bruce Korb
2010-03-01 21:23 ` Bruce Korb
2010-03-01 21:42 ` Chris Packham
2010-03-01 22:00 ` Bruce Korb
2010-03-01 22:04 ` SUCCESS -- " Bruce Korb
2010-03-02 11:44 ` Erik Faye-Lund
2010-03-02 19:09 ` Jakub Narebski
2010-03-02 21:36 ` Chris Packham
2010-03-02 23:07 ` [gitbook PATCH] add notes on re-writing history Chris Packham
2010-03-01 21:27 ` Jacob Helwig [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=2793902788222999372@unknownmsgid \
--to=jacob.helwig@gmail.com \
--cc=bkorb@gnu.org \
--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).