GDB 5.1 branch cut

GDB 5.1 branch cut

[Andrew Cagney]

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.

	Andrew

Re: GDB 5.1 branch cut

[Daniel Jacobowitz]

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

Re: GDB 5.1 branch cut

[Daniel Jacobowitz]

On Mon, Jul 30, 2001 at 10:22:27AM -0700, Daniel Jacobowitz wrote:
> > 	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?

For the curious, it appears to be a CVS bug, as those files are shared
between the gdb and dejagnu modules; check out gdb+dejagnu instead.

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

Re: GDB 5.1 branch cut

[Andrew Cagney]

> 
> 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?


CVS feature (i.e. I'm not sure who to blame).  The CVS modules DEJAGNU 
and GDB overlap so when the DEJAGNU part of the update comes through the 
local (?) CVS gets a little confused.  I probably should have specified 
``gdb+dejagnu'' which doesn't have any overlap.

	Andrew

(See `cvs -d ... co CVSROOT/modules` )