From: Kevin Daudt <me@ikke.info>
To: "Barodia, Anjali (Nokia - IN/Noida)" <anjali.barodia@nokia.com>
Cc: "repo-discuss@googlegroups.com" <repo-discuss@googlegroups.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git push error due to hooks error
Date: Mon, 14 May 2018 21:57:33 +0200 [thread overview]
Message-ID: <20180514195733.GA22721@alpha> (raw)
In-Reply-To: <AM4PR0701MB2116C3BBD0A1E4892EAB09BB8A9C0@AM4PR0701MB2116.eurprd07.prod.outlook.com>
On Mon, May 14, 2018 at 05:44:06PM +0000, Barodia, Anjali (Nokia - IN/Noida) wrote:
> Hi Support,
>
>
> I was trying to push local git to another git on gerrit, but stuck with an hook error.
> This is a very large repo and while running the command "git push origin --all"
> I am getting this errors:
>
> remote: (W) 92e19d4: too many commit message lines longer than 70 characters; manually wrap lines
> remote: (W) de2245b: too many commit message lines longer than 70 characters; manually wrap lines
> remote: (W) dc6e982: too many commit message lines longer than 70 characters; manually wrap lines
> remote: (W) d2e2efd: too many commit message lines longer than 70 characters; manually wrap lines
> remote: error: internal error while processing changes To ssh_url_path:8282/SI_VF.git
> ! [remote rejected] master -> master (Error running hook /opt/gerrit/hooks/re f-update)
> error: failed to push some refs to 'ssh_user@url_path:8282/SI_VF.git'
>
> I tried to push after deleting the .git/hooks, but still get the same error.
> Please help me in fixing this error.
>
> Thanks with Regards,
> Anjali Barodia
Did you remove the hook from the remote repo, or the local repo? Because
this is a hook which runs on the repo you are pushing too. Something
like pre-receive or pre-update is causing this.
Kevin
next prev parent reply other threads:[~2018-05-14 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 17:44 Git push error due to hooks error Barodia, Anjali (Nokia - IN/Noida)
2018-05-14 19:57 ` Kevin Daudt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-14 17:32 Barodia, Anjali (Nokia - IN/Noida)
2018-05-14 17:36 ` Martin Fick
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=20180514195733.GA22721@alpha \
--to=me@ikke.info \
--cc=anjali.barodia@nokia.com \
--cc=git@vger.kernel.org \
--cc=repo-discuss@googlegroups.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).