Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] fix test script ERRORs in 5.1 branch
Date: Sun, 13 Jan 2002 20:10:00 -0000	[thread overview]
Message-ID: <3C425A0B.90807@cygnus.com> (raw)
In-Reply-To: <20020113225315.A21807@nevyn.them.org>

> On Sun, Jan 13, 2002 at 09:47:27PM -0600, Michael Elizabeth Chastain wrote:
> 
>> I'd like to request approval to port this test script patch
>> from mainline to the 5.1 branch:
>> 
>> http://sources.redhat.com/ml/gdb-cvs/2001-10/msg00156.html
>> 
>> This looks like an obvious fix to me, but I want to be conservative about
>> changing the branch.  Note that the only changes are in test suite files.
>> 
>> My motivation: I run test suites on both mainline and 5.1 branch and
>> I write explanations of every ERROR and WARNING.  It will make my life
>> easier to remove ERRORs from the 5.1 branch, because then I won't have
>> to keep seeing them and keep checking that they are the same error as
>> the last test suite run.
> 
> 
> My impression is that Andrew's leaning more towards a 5.2 release than
> a 5.1.1 release, so I don't know if it would be worth the effort...


Or the political compromize:  Spin what ever is at the head of the  5.1 
branch as 5.1.1 while simultaneously cutting the branch for 5.2.

Michael, pulling the test cases over doesn't worry me.  Er, almost.  The 
trunk contains some recently OBSOLETE code so you'd need care there.

Andrew




  reply	other threads:[~2002-01-14  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 19:47 Michael Elizabeth Chastain
2002-01-13 19:53 ` Daniel Jacobowitz
2002-01-13 20:10   ` Andrew Cagney [this message]
2002-01-13 20:17 Michael Elizabeth Chastain

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=3C425A0B.90807@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.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