From: "Arsen Arsenović" <arsen@aarsen.me>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] contracts: Stop relying on mangling for naming .pre/.post clones
Date: Sat, 17 Dec 2022 12:30:12 +0100 [thread overview]
Message-ID: <86len6b731.fsf@aarsen.me> (raw)
In-Reply-To: <1dd4376e-84c1-c81c-415e-76c41d1e2475@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
Jason Merrill <jason@redhat.com> writes:
>
> It's best to wrap the ChangeLog entry at column 75 so that the extra
> indentation added by git log doesn't push past column 80.
>
> Applied with that change.
>
> Jason
Heh, I thought I fixed my fill-column. Will check.
Thanks!
Have a great day.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
prev parent reply other threads:[~2022-12-17 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 13:13 Arsen Arsenović
2022-12-10 13:14 ` Arsen Arsenović
2022-12-10 19:51 ` Bernhard Reutner-Fischer
2022-12-11 15:56 ` Arsen Arsenović
2022-12-15 15:40 ` Jason Merrill
2022-12-15 18:00 ` Arsen Arsenović
2022-12-15 20:29 ` Iain Sandoe
2022-12-17 11:30 ` Arsen Arsenović
2022-12-15 21:48 ` Jason Merrill
2022-12-17 11:30 ` Arsen Arsenović [this message]
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=86len6b731.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).