All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Fick <mfick@codeaurora.org>
To: "Barodia, Anjali (Nokia - IN/Noida)" <anjali.barodia@nokia.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git push error due to hooks error
Date: Mon, 14 May 2018 11:36:01 -0600	[thread overview]
Message-ID: <5444972.XKqSDWe6bT@mfick-lnx> (raw)
In-Reply-To: <AM4PR0701MB21165697A8485CA4B42ADFFB8A9C0@AM4PR0701MB2116.eurprd07.prod.outlook.com>

On Monday, May 14, 2018 05:32:35 PM Barodia, Anjali wrote:
> 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'


This is standard Gerrit behavior.  For Gerrit questions, 
please post question to:

Repo and Gerrit Discussion <repo-discuss@googlegroups.com>

-Martin

-- 
The Qualcomm Innovation Center, Inc. is a member of Code 
Aurora Forum, hosted by The Linux Foundation


  reply	other threads:[~2018-05-14 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 17:32 Git push error due to hooks error Barodia, Anjali (Nokia - IN/Noida)
2018-05-14 17:36 ` Martin Fick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-14 17:44 Barodia, Anjali (Nokia - IN/Noida)
2018-05-14 19:57 ` Kevin Daudt

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=5444972.XKqSDWe6bT@mfick-lnx \
    --to=mfick@codeaurora.org \
    --cc=anjali.barodia@nokia.com \
    --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 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.