public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Mike Stump <mikestump@comcast.net>,
	       Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, testsuite] Allow braces around relative line numbers
Date: Tue, 28 Mar 2017 22:24:00 -0000	[thread overview]
Message-ID: <20170328222321.GE17461@tucnak> (raw)
In-Reply-To: <31cf86fd-eda4-e373-5263-a3b36854109e@mentor.com>

On Tue, Mar 28, 2017 at 08:27:54AM +0200, Tom de Vries wrote:
> this patch fixes testsuite PR80220 - "relative line numbers don't work when
> put between braces".

What is the advantage of putting the line numbers between braces?
Isn't it easier to just drop those?

	Jakub

  reply	other threads:[~2017-03-28 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  7:45 Tom de Vries
2017-03-28 22:24 ` Jakub Jelinek [this message]
2017-04-15  8:34   ` Tom de Vries
2017-04-15 15:54     ` Mike Stump

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=20170328222321.GE17461@tucnak \
    --to=jakub@redhat.com \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).