Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Dave Korn <dave.korn.cygwin@gmail.com>, Hui Zhu <teawater@gmail.com>
Subject: Re: Question about "cvs update"
Date: Mon, 11 Oct 2010 16:43:00 -0000	[thread overview]
Message-ID: <201010111743.00605.pedro@codesourcery.com> (raw)
In-Reply-To: <4CB34085.1010102@gmail.com>

On Monday 11 October 2010 17:51:17, Dave Korn wrote:
> On 11/10/2010 08:49, Hui Zhu wrote:
> > Hi guys,
> > 
> > "cvs update -d" will make the src directory include a lot of other
> > softwares like binutils, sid and so on.
> > 
> > I want keep the directory just have the file of GDB.  I tried "cvs
> > update -dP".  But it still tried to checkout the files of other
> > softwares.
> > 
> > Could someone tell me how to update the all src directory and do not
> > co the files of other softwares.
> 
>   I do something roughly(*) like:
> 
> ls -1d */CVS | cut -d/ -f1 | xargs cvs up -dP
> 
> ... followed by a plain old "cvs up" to get the top-level files.  This can
> easily be put into a shell alias or function definition in one of your shell
> startup scripts.

Irks.  I just do "cvs co" which knows to update instead of
checkout if you already have a tree, but wrapped in a tiny script
that I carry around to all my trees:

 $ cat /home/pedro/gdb/baseline/cvsup.sh 
 #!/bin/bash

 cvs -t -d :ext:palves@sourceware.org:/cvs/src co gdb

That's it!

To avoid hacks, I just have my sources in a directory
called literally "src".  E.g., I follow this layout:

 /home/pedro/gdb/baseline/src
 /home/pedro/gdb/baseline/build
 /home/pedro/gdb/baseline/cvsup.sh 

and 

 /home/pedro/gdb/foo-project/src
 /home/pedro/gdb/foo-project/build
 /home/pedro/gdb/foo-project/cvsup.sh 

etc.

When I want to update a tree, I just e.g.,

 $ cd /home/pedro/gdb/baseline
 $ ./cvsup.sh

When I want to create a new fresh checkout, I do:

 $ mkdir /home/pedro/gdb/fresh-project
 $ cd /home/pedro/gdb/fresh-project
 $ cp /home/pedro/gdb/baseline/cvsup.sh /home/pedro/gdb/fresh-project
 $ ./cvsup.sh

(or copy an existing tree)

I prefer copying the script file because sometimes I want to checkout
a specific date / tag / branch.  E.g.,

 $ cat /home/pedro/gdb/7_0/cvsup.sh
 #!/bin/bash
 cvs -t -z9 -d :ext:palves@sourceware.org:/cvs/src co -r gdb_7_0-branch gdb

-- 
Pedro Alves


      reply	other threads:[~2010-10-11 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  7:50 Hui Zhu
2010-10-11  7:56 ` Jan Kratochvil
2010-10-11  8:10   ` Hui Zhu
2010-10-11 15:25 ` Christopher Faylor
2010-10-11 18:59   ` Steffen DETTMER
2010-10-11 15:32 ` Daniel Jacobowitz
2010-10-11 16:28 ` Dave Korn
2010-10-11 16:43   ` Pedro Alves [this message]

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=201010111743.00605.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dave.korn.cygwin@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=teawater@gmail.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