From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, Tom King <ka6sox@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: OE-Core repo broken again
Date: Tue, 17 May 2011 12:11:05 +0100 [thread overview]
Message-ID: <1305630665.3424.227.camel@rex> (raw)
Hi Guys,
Something is broken with the oe-core repository as I can't push to it:
$ git push origin master:master
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 628 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
remote: sed: can't read ./description: No such file or directory
remote: *** Project description file hasn't been set
remote: error: hook declined to update refs/heads/master
To ssh://git@git.openembedded.org/openembedded-core
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'ssh://git@git.openembedded.org/openembedded-core'
Cheers,
Richard
next reply other threads:[~2011-05-17 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 11:11 Richard Purdie [this message]
2011-05-17 16:56 ` OE-Core repo broken again Khem Raj
2011-05-17 17:22 ` Richard Purdie
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=1305630665.3424.227.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=ka6sox@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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