From: Stephen Berman <stephen.berman@gmx.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: 23481@debbugs.gnu.org
Subject: bug#23481: 25.1.50; vc-next-action cannot commit for emacs master
Date: Sun, 08 May 2016 22:15:12 +0200 [thread overview]
Message-ID: <87oa8gwblb.fsf@gmx.net> (raw)
In-Reply-To: <87poswuyfq.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 08 May 2016 19:44:41 +0000")
On Sun, 08 May 2016 19:44:41 +0000 Uwe Brauer <oub@mat.ucm.es> wrote:
> > That's strange. When I tried your recipe, I did see that message.
>
>
> > Your log message should have a one-line summary line, then an empty
> > line, then the rest of the log. See CONTRIBUTE, where all this is
> > explained in more detail.
>
>
> > Put some summary text after "Summary:", then add an empty line after
> > "Author:" (I think deleting "Author:" is also okay, but there should
> > be an empty line after the "------" line.
>
>
> Thanks! that worked, (well git complained about some whitespace added,
> but what the heck, so I had to delete those, I presume that is for the
> diffs, ). Thanks for your help.
AFAIK it's not necessary for there to be an empty line after the line
below the "Author:" field in the *vc-log* buffer, as long as the
"Summary:" field is filled in. At least, that's what I always do and
git has not complained to me about it. I assume some VC code adds the
empty line when the "Summary:" field is filled in.
Steve Berman
next prev parent reply other threads:[~2016-05-08 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 17:27 bug#23481: 25.1.50; vc-next-action cannot commit for emacs master Uwe Brauer
2016-05-08 18:05 ` Eli Zaretskii
2016-05-08 18:19 ` Uwe Brauer
2016-05-08 18:47 ` Eli Zaretskii
2016-05-08 19:44 ` Uwe Brauer
2016-05-08 20:15 ` Stephen Berman [this message]
2016-05-09 2:25 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa8gwblb.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=23481@debbugs.gnu.org \
--cc=oub@mat.ucm.es \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).