public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add support for embedding scripts in .debug_gdb_scripts.
Date: Mon, 19 Jan 2015 14:49:00 -0000	[thread overview]
Message-ID: <20150119144921.GC4041@adacore.com> (raw)
In-Reply-To: <CAP9bCMTbhAc-BfFTCb_mLyEWFo2soPxS=5dq0AW8qT0s-hxiAg@mail.gmail.com>

> >> All NEWS entries for new features shall specify the platform(s) on which
> >> the feature is available, if it is not a generally available feature.
> >> [or words to that effect]
> >> And let's enforce all these rules the way we do
> >> coding conventions (which I don't have a problem with).
> >>
> >> Ok?
> >
> > I'm fine with that, if no one objects.  But you cannot possibly codify
> > all such minor issues, they are too many.  And it isn't needed, from
> > my POV.
> 
> If it serves to put in writing absolute rules that someone is likely
> to get tripped up by or not understand then it will have served its
> purpose.

I just personally think this is too extreme a measure.  There are times
when absolute rules may be useful, but I don't think this is the case
here.

Eli is our documentation maintainer,so let's continue trusting
his judgement. This discussion is not about black and white, and
as such, it's easy to disagree. But I don't think it's important
enough to spend more time on this. I know it can be fustrating
to make a change one does not believe in, but after a reasonable
attempt at discussing it, I'd go with his call.

-- 
Joel

  reply	other threads:[~2015-01-19 14:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 17:32 Doug Evans
2015-01-15 18:11 ` Eli Zaretskii
2015-01-16 17:15   ` Doug Evans
2015-01-16 18:02     ` Eli Zaretskii
2015-01-17  1:16       ` Doug Evans
2015-01-17  8:16         ` Eli Zaretskii
2015-01-18  4:16           ` Doug Evans
2015-01-18 16:23             ` Eli Zaretskii
2015-01-18 20:48               ` Doug Evans
2015-01-19 14:49                 ` Joel Brobecker [this message]
2015-01-20 16:35                   ` Doug Evans
2015-01-21  9:57                     ` Joel Brobecker
2015-02-13 16:15                     ` Stan Shebs
2015-02-13 16:45                       ` Eli Zaretskii
2015-02-13 16:46                       ` Andreas Schwab
2015-02-13 18:05                     ` Pedro Alves
2015-02-15 11:53                       ` Corinna Vinschen
2015-01-19 16:05                 ` Eli Zaretskii
2015-01-31 23:31 ` Doug Evans

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=20150119144921.GC4041@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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).