Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: Trimming the CVS "gdb" module
Date: Wed, 06 Oct 2004 16:45:00 -0000	[thread overview]
Message-ID: <416420FF.2090201@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 606 bytes --]

Following tries to close a number of random discussions that noticed 
that the GDB module contains stuff that is no longer applicable.

The attached modifies GDB's "gdb" CVS module trimming it back to what is 
currently relevant.  It drops mmalloc/ (not used), cgen/cpu/ (moved to 
cpu/), intl (use installed), and utils/ (not used).

It also adds the module old-gdb which retains all the old directories 
and hence can be used to check out old gdb versions (although "gdb" will 
be sufficient for most needs).

I'll look to commit this in a week, this needs to be closed before 6.3 
is branched.

Andrew


[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1481 bytes --]

? diffs
Index: modules
===================================================================
RCS file: /cvs/src/CVSROOT/modules,v
retrieving revision 1.56
diff -p -u -r1.56 modules
--- modules	30 Mar 2004 01:35:57 -0000	1.56
+++ modules	6 Oct 2004 16:36:49 -0000
@@ -128,14 +128,22 @@ sim		-a naked-sim naked-bfd naked-opcode
 		naked-libiberty naked-mmalloc naked-include \
 		src-support naked-intl
 
-naked-gdb-guifull -a src/gdb
-naked-gdb	-a !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb
-gdb-support	-a naked-texinfo naked-bfd naked-opcodes \
+# OLD-GDB contains everything that ever was in GDB.  It can be used to
+# check out out old GDB branches and as an approximation for an old
+# mainline.
+old-gdb		-a !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb \
+		naked-texinfo naked-bfd naked-opcodes \
 		naked-readline naked-libiberty naked-mmalloc naked-include \
 		naked-sim naked-utils src-support naked-intl naked-cpu \
-		src/cgen/cpu \
-		src/djunpack.bat
+		src/cgen/cpu src/djunpack.bat
 
+naked-gdb-guifull -a src/gdb
+naked-gdb	-a !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb
+gdb-support	-a naked-texinfo naked-bfd naked-opcodes \
+		naked-readline naked-libiberty naked-include \
+		naked-sim naked-utils naked-cpu src/djunpack.bat \
+		src-support
+# Module reflecting active development.
 gdb		-a naked-gdb gdb-support
 gdb+dejagnu	-a gdb naked-dejagnu naked-expect naked-tcl
 gdb+binutils	-a gdb naked-binutils naked-gas naked-gprof naked-ld

             reply	other threads:[~2004-10-06 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 16:45 Andrew Cagney [this message]
2004-10-08 10:10 ` Eli Zaretskii
2004-10-13  4:52   ` Andrew Cagney
2004-10-13 13:45     ` Eli Zaretskii
2004-10-14  4:48       ` Mark Kettenis
2004-10-14  4:53         ` Eli Zaretskii
2004-10-19 19:55           ` Andrew Cagney
2004-10-19 20:34             ` Eli Zaretskii
2004-10-19 22:55               ` Mark Kettenis
2004-10-20  2:29                 ` Eli Zaretskii
2004-10-20  4:52               ` Andrew Cagney
2004-10-20 15:11                 ` Eli Zaretskii
2004-10-20 18:29                   ` Andrew Cagney
2004-10-20 22:21                     ` Eli Zaretskii
2004-10-20 23:25                       ` Daniel Jacobowitz
2004-10-21 14:51                         ` Eli Zaretskii
2004-10-22 10:09                           ` Daniel Jacobowitz
2004-10-19 18:28 ` Andrew Cagney

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=416420FF.2090201@gnu.org \
    --to=cagney@gnu.org \
    --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