From: "Carlos Martín Nieto" <cmn@elego.de>
To: salmanmanekia <salmanmanekia@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Submodule would not work. The push does not work
Date: Fri, 29 Jun 2012 05:36:10 +0200 [thread overview]
Message-ID: <1340940970.21992.1.camel@centaur.cmartin.tk> (raw)
In-Reply-To: <1340924055050-7562323.post@n2.nabble.com>
On Thu, 2012-06-28 at 15:54 -0700, salmanmanekia wrote:
> I have been trying to create a submodule in git After issuing the git
> submodule init i see the folders for the submodule. After that i add, commit
> and try to push those files in the master repo but it would not allow me to
> do soo
This doesn't seem to be related to submodules.
>
> Salman@PC_HOME ~/git/breakit-web-app (master)
> $ git push origin master
> error: refs/heads/master does not point to a valid object!
> Counting objects: 4, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (3/3), 421 bytes, done.
> Total 3 (delta 1), reused 0 (delta 0)
> remote: bb/acl: salmanmanekia is allowed. accepted payload.
> error: Ref refs/heads/master is at 6a47a0fd398610a75bdab8976f842dc0efd89f86
> but expected 00000000000000000000000000000000000000000
> remote: error: failed to lock refs/heads/master
>
> To ssh://git@bitbucket.org/majuri/breakit-web-app.git
> ! [remote rejected] master -> master (failed to lock)
> error: failed to push some refs to
> 'ssh://git@bitbucket.org/majuri/breakit-web-app.git'
There error messages come from a hook being run on the bitbucket
servers. They're the only ones who can know what they mean and how to
solve it.
cmn
next prev parent reply other threads:[~2012-06-29 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 22:54 Git Submodule would not work. The push does not work salmanmanekia
2012-06-29 3:36 ` Carlos Martín Nieto [this message]
2012-06-29 7:18 ` salmanmanekia
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=1340940970.21992.1.camel@centaur.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=salmanmanekia@gmail.com \
/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).