From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Development <gcc@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: git: remote: *** The first line of a commit message should be a short description of the change, not a single word.
Date: Tue, 21 Jan 2020 16:58:00 -0000 [thread overview]
Message-ID: <CAH6eHdRad1wHeok6=DLh+B8HMGdi-s=o5wsqcKTTaMV67TDXhw@mail.gmail.com> (raw)
In-Reply-To: <ca530e15-5157-3f17-9c97-10d99a63a193@suse.cz>
On Tue, 21 Jan 2020 at 16:03, Martin Liška <mliska@suse.cz> wrote:
>
> Can you please remove the hook for user branches likes:
>
> $ git push origin me/filter-non-common
> Enumerating objects: 27, done.
> Counting objects: 100% (27/27), done.
> Delta compression using up to 16 threads
> Compressing objects: 100% (14/14), done.
> Writing objects: 100% (14/14), 1.77 KiB | 1.77 MiB/s, done.
> Total 14 (delta 13), reused 0 (delta 0)
> remote: *** The first line of a commit message should be a short description of the change, not a single word.
> remote: error: hook declined to update refs/users/marxin/heads/filter-non-common
> To git+ssh://gcc.gnu.org/git/gcc.git
> ! [remote rejected] me/filter-non-common -> refs/users/marxin/heads/filter-non-common (hook declined)
> error: failed to push some refs to 'git+ssh://gcc.gnu.org/git/gcc.git'
Requiring slightly better messages than just a single word doesn't
seem to restrictive to me, even on user branches.
next prev parent reply other threads:[~2020-01-21 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 16:45 Martin Liška
2020-01-21 16:58 ` Jonathan Wakely [this message]
2020-01-21 17:05 ` Richard Earnshaw (lists)
2020-01-21 17:20 ` Nathan Sidwell
2020-01-21 17:31 ` Richard Earnshaw (lists)
2020-01-21 18:58 ` Jason Merrill
2020-01-21 19:58 ` Jonathan Wakely
2020-01-22 9:26 ` Martin Liška
2020-01-22 9:38 ` Richard Biener
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='CAH6eHdRad1wHeok6=DLh+B8HMGdi-s=o5wsqcKTTaMV67TDXhw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=mliska@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).