Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com, xyzzy@hotpop.com
Subject: Re: binutils+gdb CVS module
Date: Mon, 18 Aug 2003 10:34:00 -0000	[thread overview]
Message-ID: <200308181034.h7IAYdbE031302@duracef.shout.net> (raw)

Hi Stephen,

> How does one know when there is something new?  Add a watch via email? 
> Is that even allowed with this repository?

Watches are a big dead end as far I can tell.  They only work on files,
not on directories, and they require other people to do 'cvs edit'
to send the signal.  Anyways, gdb doesn't use them.

The usual procedure is to subscribe to gdb-cvs mailing list and
watch the commits go by.  Also, if your work area starts mysteriously
failing, look in the gdb mailing list and see if people are talking
about another round of top level changes.

AFAIK, the most recent new file was src-release on 2002-10-01.  So 'cvs
update' will fail about once a year.  Less, really, for an ordinary gdb
developer who is not making releases or editing the configuration
machinery (editing Makefile.tpl and stuff).

Me, I just do fresh "cvs checkout" a lot.  But I do more testing
than developing.

Michael C


             reply	other threads:[~2003-08-18 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 10:34 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18  9:04 Michael Elizabeth Chastain
2003-08-18 10:09 ` Stephen Biggs
2003-08-18 12:56 ` Daniel Jacobowitz
2003-08-18 13:03   ` Bob Rossi
2003-08-18 14:51   ` Stephen Biggs
2003-08-18 14:54     ` Daniel Jacobowitz
2003-08-18 15:10       ` Stephen Biggs
2003-08-18  8:10 Stephen Biggs

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=200308181034.h7IAYdbE031302@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb@sources.redhat.com \
    --cc=xyzzy@hotpop.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