Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Michael Snyder'" <msnyder@vmware.com>, <gdb-patches@sourceware.org>
Subject: RE: [patch] Shorten lines of >= 80 columns.
Date: Tue, 04 Jan 2011 19:19:00 -0000	[thread overview]
Message-ID: <000c01cbac44$48830210$d9890630$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4D237089.1080309@vmware.com>

I thought that they were already considered as obvious,
but I still have a remark about one of your
changes:

@@ -632,8 +633,8 @@ gen_var_ref (struct gdbarch *gdbarch, st
       break;
 
     case LOC_CONST_BYTES:
-      internal_error (__FILE__, __LINE__,
-		      _("gen_var_ref: LOC_CONST_BYTES symbols are not
supported"));
+      internal_error (__FILE__, __LINE__, _("\
+gen_var_ref: LOC_CONST_BYTES symbols are not supported"));

I think this kind of changes confuses cvs
for the 'cvs diff -u -p':
it might regard the new line
+gen_var_ref: LOC_CONST_BYTES symbols are not supported"));
as a new starting function line and
report a wrong function name...
Of course not really for your example here,
as the start of the line is
the name of the function itself...
But I remember having seen
wrong function name reported with 'cvs -u -p'
due to the use of '_("\'
construct which force starting next line without 
spaces...

Pierre Muller
GDB pascal language maintainer

 
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Michael Snyder
> Envoyé : mardi 4 janvier 2011 20:10
> À : gdb-patches@sourceware.org
> Objet : [patch] Shorten lines of >= 80 columns.
> 
> I would like to propose that this type of change be regarded as
> "obvious".



  reply	other threads:[~2011-01-04 19:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 19:10 Michael Snyder
2011-01-04 19:19 ` Pierre Muller [this message]
2011-01-04 20:00   ` Michael Snyder
2011-01-05  9:02     ` Pierre Muller
2011-01-05 18:25       ` Michael Snyder
2011-01-05 21:38         ` Michael Snyder
2011-01-06  4:32           ` Joel Brobecker
2011-01-06 18:05             ` Michael Snyder
2011-01-04 19:27 ` Mark Kettenis

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='000c01cbac44$48830210$d9890630$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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