Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] include/gdb/signals.h
Date: Sun, 10 Mar 2002 16:02:00 -0000	[thread overview]
Message-ID: <20020310190211.A13023@nevyn.them.org> (raw)
In-Reply-To: <3C8BDDAB.9020504@cygnus.com>

On Sun, Mar 10, 2002 at 05:26:51PM -0500, Andrew Cagney wrote:
> 
> >>There should also be an entry for src/include/ChangeLog indicating the 
> >>presence of the new directory.
> >
> >
> >Good thought.  Since DJ said it wouldn't cause a problem, shall I
> >commit this?
> 
> Commit to src, yep.
> 
> I'm trying to figure out if DJ's reply:
> 
> >I'm just wondering how DJ would react to the addition of an entry in 
> >>gcc/include/ChangeLog there isn't a corresponding directory (gcc/include 
> >>is the master yet really it isn't :-)
> >
> >
> >Not a problem.  The scripts ignore anything in src that isn't also in
> >gcc, and this wouldn't be the first ignored subdirectory.
> 
> is an ok to also commit the ChangeLog entry to the GCC include 
> directory.  I guess it is a doesn't matter.  Come the revolution 
> (GCC+GDB merge) I'd like to try to avoid a merge that looses src/include 
> related ChangeLog entries.

Committed.  DJ tells me that the scripts which sync the two include
directories will properly ignore ChangeLog entries (neat!) for things
which are not in both repositories.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-03-11  0:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-10  9:26 Daniel Jacobowitz
2002-03-10 11:52 ` Andrew Cagney
2002-03-10 14:06   ` DJ Delorie
2002-03-10 14:10   ` Daniel Jacobowitz
2002-03-10 14:26     ` Andrew Cagney
2002-03-10 16:02       ` Daniel Jacobowitz [this message]

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=20020310190211.A13023@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.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