From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] ChangeLog width 74 -> 80
Date: Tue, 18 Jun 2013 21:35:00 -0000 [thread overview]
Message-ID: <20130618210910.GC5560@adacore.com> (raw)
In-Reply-To: <20130618175322.GA490@host2.jankratochvil.net>
FWIW, I find 80 characters to be too long, and more difficult to read.
I thought 74 characters was a good compromise, so why not standardize
on that?
--
Joel
next prev parent reply other threads:[~2013-06-18 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:09 Jan Kratochvil
2013-06-18 15:30 ` Pedro Alves
2013-06-18 15:34 ` Jan Kratochvil
2013-06-18 15:47 ` Pedro Alves
2013-06-18 15:51 ` Jan Kratochvil
2013-06-18 16:22 ` Pedro Alves
2013-06-18 18:02 ` Jan Kratochvil
2013-06-18 21:35 ` Joel Brobecker [this message]
2013-06-19 13:25 ` [cancel] " Jan Kratochvil
2013-06-19 7:50 ` Yao Qi
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=20130618210910.GC5560@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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