Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb@sources.redhat.com
Subject: Re: Delete .texi files from trunk?
Date: Thu, 01 Nov 2001 09:13:00 -0000	[thread overview]
Message-ID: <3BEF305F.9040300@cygnus.com> (raw)
In-Reply-To: <3BEED1DE.50205@cygnus.com>

After the release process the tree looks like this:

[gdbadmin@sourceware src]$ cvs update
cvs update: Updating .
M djunpack.bat
? proto-toplev
? gdb-5.0.93.tar.bz2
cvs update: Updating bfd
...
cvs update: Updating bfd/po
cvs update: warning: bfd/po/BLD-POTFILES.in was lost
U bfd/po/BLD-POTFILES.in
cvs update: warning: bfd/po/SRC-POTFILES.in was lost
U bfd/po/SRC-POTFILES.in
cvs update: Updating config
...
cvs update: Updating gdb
M gdb/version.in
? gdb/p-exp.tab.c
cvs update: Updating gdb/29k-share
...
cvs update: Updating gdb/doc
? gdb/doc/gdb.info-11
? gdb/doc/gdb.info-12
? gdb/doc/gdb.info-13
? gdb/doc/gdb.info-14
? gdb/doc/gdb.info-15
? gdb/doc/gdbint.info-4
? gdb/doc/gdbint.info-5
cvs update: Updating gdb/gdbserver
? gdb/gdbserver/config.log
? gdb/gdbserver/config.status
? gdb/gdbserver/Makefile
cvs update: Updating gdb/mi
...


So several strange things:
	- those poo files being deleted
	- some .info files reported (others weren't)
	- gdbserver containing crud
so more digging is required.

Andrew


      reply	other threads:[~2001-11-12  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01  4:52 Andrew Cagney
2001-11-01  8:24 ` Eli Zaretskii
2001-11-01  8:35   ` Andrew Cagney
2001-11-01  9:13     ` Andrew Cagney [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=3BEF305F.9040300@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@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