Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] ChangeLog width 74 -> 80
Date: Tue, 18 Jun 2013 15:51:00 -0000	[thread overview]
Message-ID: <20130618154752.GA27499@host2.jankratochvil.net> (raw)
In-Reply-To: <51C07FCC.6090706@redhat.com>

On Tue, 18 Jun 2013 17:42:04 +0200, Pedro Alves wrote:
> Nobody said anything about bugs.  Nor is emacs a non-modern editor.

I do not understand why you have mentioned Emacs in the first place, it seems
irrelevant for GDB development.

I find correct to update existing Emacs rules to comply with the specification
but I do not think it matters to mention Emacs when deciding what should be
the GDB standard.


> As I said, I really don't care that much about the precise width.
> It'd be nice to have it changed consistently across the tree
> though.

One should define first what is "the tree", currently it contains many
directions which seems irrelevant for GDB decisions to me (tcl, texinfo,
newlib, rda, ...).

And even in that case GDB already contains Coding Style in gdbint.texinfo
specific only to gdb/ so unifying the ChangeLog standard across the tree
(whatever that means) is only that "nice to have", not a requirement.


Jan


  reply	other threads:[~2013-06-18 15:47 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 [this message]
2013-06-18 16:22         ` Pedro Alves
2013-06-18 18:02           ` Jan Kratochvil
2013-06-18 21:35             ` Joel Brobecker
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=20130618154752.GA27499@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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