This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Difficulty for community involvment in gdb

To: erl at voxi dot com
Subject: Re: Difficulty for community involvment in gdb
From: DJ Delorie <dj at redhat dot com>
Date: Thu, 2 Aug 2001 12:13:26 -0400
CC: gdb at sources dot redhat dot com
References: <3B684397.40704@voxi.com> <3B686235.30809@cygnus.com> <3B693AC7.4050106@voxi.com>


>   My standard way of getting changes from a cvs repository is to type: 
> "cvs -q update -Pd". This also retrieves new directories. In all other 

A more correct way to update a module set is to do this:

	cvs -q get gdb

Unless your cvs is quite old, this *is* an incremental update *plus*
any new directories *defined by the module*.  You can't do that with
"cvs update".

References:
- Difficulty for community involvment in gdb
  - From: Erland Lewin
- Re: Difficulty for community involvment in gdb
  - From: Andrew Cagney
- Re: Difficulty for community involvment in gdb
  - From: Erland Lewin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]