[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

gEDA-cvs: gaf.git: branch: master updated (1.5.2-20090328-81-gb8c503e)



The branch, master has been updated
       via  b8c503e7b1bfa7b797abac53d073ceab4779fbb1 (commit)
      from  a9eac3fbe1057859ddd44304d72aa86407fdb548 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


=========
 Summary
=========

 gnetlist/src/gnetlist.c |    9 ---------
 1 files changed, 0 insertions(+), 9 deletions(-)


=================
 Commit Messages
=================

commit b8c503e7b1bfa7b797abac53d073ceab4779fbb1
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>

    Don't recommend drc2 every time gnetlist runs.
    
    On Thursday 11 June 2009 17:48:48 John Doty wrote:
    > drc2 has a very narrow view of how the world works. If you are doing
    > a pure digital design using a single logic family using hidden power
    > pins, it's not *too* bad. But generally, it hides real errors behind
    > a flood of messages about things that aren't errors at all. gEDA is
    > much more flexible than drc2 understands. It's generally only useful
    > if you've learned to find the few real issues in the flood.
    >
    > DEVELOPERS:
    >
    > WHY DO WE RECOMMEND THIS FLAWED, NARROW, EXPERT TOOL, REPEATEDLY AND
    > OBNOXIOUSLY, TO ALL WHO USE GNETLIST, EVERY TIME THEY USE IT?

:100644 100644 ac4966b... d18a925... M	gnetlist/src/gnetlist.c

=========
 Changes
=========

commit b8c503e7b1bfa7b797abac53d073ceab4779fbb1
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>

    Don't recommend drc2 every time gnetlist runs.
    
    On Thursday 11 June 2009 17:48:48 John Doty wrote:
    > drc2 has a very narrow view of how the world works. If you are doing
    > a pure digital design using a single logic family using hidden power
    > pins, it's not *too* bad. But generally, it hides real errors behind
    > a flood of messages about things that aren't errors at all. gEDA is
    > much more flexible than drc2 understands. It's generally only useful
    > if you've learned to find the few real issues in the flood.
    >
    > DEVELOPERS:
    >
    > WHY DO WE RECOMMEND THIS FLAWED, NARROW, EXPERT TOOL, REPEATEDLY AND
    > OBNOXIOUSLY, TO ALL WHO USE GNETLIST, EVERY TIME THEY USE IT?

diff --git a/gnetlist/src/gnetlist.c b/gnetlist/src/gnetlist.c
index ac4966b..d18a925 100644
--- a/gnetlist/src/gnetlist.c
+++ b/gnetlist/src/gnetlist.c
@@ -168,15 +168,6 @@ void main_prog(void *closure, int argc, char *argv[])
     fprintf(stderr, "This is the MINGW32 port.\n\n");
 #endif
 
-    s_log_message ("Remember to check that your schematic has no errors using the drc2 backend.\n");
-    s_log_message ("You can do it running 'gnetlist -g drc2 your_schematic.sch -o drc_output.txt'\n");
-    s_log_message ("and seeing the contents of the file drc_output.txt.\n\n");
-
-    if (!quiet_mode) {
-      fprintf (stderr, "Remember to check that your schematic has no errors using the drc2 backend.\n");
-      fprintf (stderr, "You can do it running 'gnetlist -g drc2 your_schematic.sch -o drc_output.txt'\n");
-      fprintf (stderr, "and seeing the contents of the file drc_output.txt.\n\n");
-    }
     /* register guile (scheme) functions */
     g_register_funcs();
 




_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs