From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, Michael Snyder <msnyder@redhat.com>,
gdb@sources.redhat.com
Subject: Re: Changing the C/C++ compiler for gdb testsuite runs
Date: Fri, 11 Jan 2002 07:38:00 -0000 [thread overview]
Message-ID: <200201111538.PAA25137@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 11 Jan 2002 10:26:33 EST." <3C3F0429.6070009@cygnus.com>
>
> > But since they don't come from the same CVS tree, I can't see how to do
> > that cleanly without dicking around with the common code directories such
> > as libiberty and include -- experience has shown that with the public CVS
> > repositories that is fraught with problems. I have done it in the past,
> > but it breaks the principal that the sources you are testing are the
> > sources you are committing, so it isn't really a viable option.
>
>
> Is the experience recent? At present mechanical processes help to
> ensure that liberty and include are kept very much in sync (typically
> only hours separate commits).
>
> Andrew
>
Well it can happen at any time when one product is coming off a branch and
the other of the trunk (or a different branch). When gcc forks (or gdb
forks) there is bound to be divergence (for obvious reasons).
R.
next prev parent reply other threads:[~2002-01-11 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 5:46 Richard Earnshaw
2002-01-10 17:30 ` Michael Snyder
2002-01-11 2:23 ` Richard Earnshaw
2002-01-11 7:26 ` Andrew Cagney
2002-01-11 7:38 ` Richard Earnshaw [this message]
2002-01-11 7:45 ` Andrew Cagney
2002-01-10 8:58 Michael Elizabeth Chastain
2002-01-10 11:10 ` Kevin Buettner
2002-01-10 11:30 ` Daniel Jacobowitz
2002-01-15 10:24 ` Daniel Jacobowitz
2002-01-15 11:18 ` Andrew Cagney
2002-01-11 8:07 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=200201111538.PAA25137@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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