Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: GDB 5.1 branch cut
Date: Mon, 30 Jul 2001 10:22:00 -0000	[thread overview]
Message-ID: <20010730102227.A6743@nevyn.them.org> (raw)
In-Reply-To: <3B636DC3.8090207@cygnus.com>

On Sat, Jul 28, 2001 at 09:58:27PM -0400, Andrew Cagney wrote:
> The branch tag used was:  gdb_5_1-2001-07-29-branch
> The branchpoint was marked with: gdb_5_1-2001-07-29-branchpoint
> 
> The branch should contain gdb/dejagnu or insight/dejagnu (depending on 
> your view pont :-).
> 
> I'm still running around updating various things.
> 
> The fastest way to get your source tree onto the branch is to execute 
> something like:
> 
> 	ls -d GDB/src
> 	mkdir 51
> 	( cd GDB && tar cf - src ) | ( cd 51 && tar xpf - )
> 	cd 51
> 	cvs -d `cat src/CVS/Root` co -r gdb_5_1-2001-07-29-branch gdb dejagnu
> 
> i.e. do a CVS co over the top of an existing CVS repository.

Interestingly, if you do this, you (or at least I) will get things
like:

cvs checkout: move away src/config/mpw/ChangeLog; it is in the way
C src/config/mpw/ChangeLog

for all the contents of src/config/mpw, src/libiberty/config, and
src/include/*/ (but not src/include itself).  Anyone know what might
cause that?

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


  reply	other threads:[~2001-07-30 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-28 18:58 Andrew Cagney
2001-07-30 10:22 ` Daniel Jacobowitz [this message]
2001-07-30 10:33   ` Daniel Jacobowitz
2001-07-30 10:55   ` Andrew Cagney

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=20010730102227.A6743@nevyn.them.org \
    --to=dmj+@andrew.cmu.edu \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=insight@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