Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Fix NATDEPFILES sed expression to comment out cont's
Date: Fri, 10 May 2002 16:50:00 -0000	[thread overview]
Message-ID: <3CDC5CB5.3020308@cygnus.com> (raw)
In-Reply-To: <20020510145819.K3435@dr-evil.shagadelic.org>

> The following was submitted as a bug report to NetBSD.  The sed
> expression that comments out NATDEPFILES does not comment out
> continuation lines.  BSD's make(1) doesn't like this (the \ at
> the end of the line is ignored, just as the rest of the line following
> the comment character is, as it should be).
> 
> The following tweak to the sed expression fixes the problem by also
> commenting out continuation lines.
> 
> Before:
> 
> # NATDEPFILES=infptrace.o inftarg.o fork-child.o \
> 	corelow.o \
> 	alphabsd-nat.o alphanbsd-nat.o
> 
> After:
> 
> # NATDEPFILES= infptrace.o inftarg.o fork-child.o \
> #	corelow.o \
> #	alphabsd-nat.o alphanbsd-nat.o
> 
> OK to commit?

Hmm, yes.  Can you just use a ``From ..'' style changelog with the 
commit.  Definitly small enough to fit under the (C) wire.

(Any developer can post then [pause] commit Makefile.in or configure.in 
changes.)

> 2002-05-10  Christian Limpach  <chris@Pin.LU>
> 
> 	* configure.in: Change sed expression which comments out
> 	NATDEPFILES to also comment out continuation lines.
> 	* configure: Regenerate.
> 

Andrew




  reply	other threads:[~2002-05-10 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10 14:58 Jason R Thorpe
2002-05-10 16:50 ` Andrew Cagney [this message]
2002-05-10 17:40   ` Jason R Thorpe

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=3CDC5CB5.3020308@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.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