public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Skeezics Boondoggle <skeezics@q7.com>
To: Hans Ronne <hronne@telia.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Map drawing glitch in latest CVS snapshot
Date: Wed, 02 Jul 2003 18:08:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0307021051330.7849-100000@q7.q7.com> (raw)
In-Reply-To: <l03130302bb283f54a3df@[212.181.162.155]>

On Wed, 2 Jul 2003, Hans Ronne wrote:

> There is a much easier way. Use cvs -D date. Start with a date midway
> between September 02 and now. Build xconq and check if the bug is there.
> Then pick a second date between that date and one of the first two. And so
> on. Typically, a handful of checkouts (less than one hour of work) can
> pinpoint exactly when the bug first appeared.

Yeah, that makes sense.  I was hoping to maybe understand the code and 
just produce a patch :-) but if I can at least help pinpoint when things 
changed/broke, maybe that'll help.

> This is something only you (or somebody else with Solaris) can do. Without
> this information, there is little I can do. I made a large number of
> changes in the tcltk interface in the last few months, and it is impossible
> for me to tell which one of them causes problems under Solaris.

The updates are much appreciated - especially in the networking code.  On
those rare occasions when I can pull my son away from his whizzy 3D
multi-player shoot'em'ups to go a few rounds on the old Sparcstation (or
now with Apple's X11 available for MacOSX) it's fun to torture him with a
game that requires a little more thought, strategy and patience than the
typical twitchy FPS games so prevalent today.  He can whoop me at Quake3
but can't even come close at MazeWar... go figure. :-)  And xconq proves 
that "old age and treachery overcomes youth and skill."  Heh heh.

I'll post more info when I've had time to do some more test builds.

Cheers,

-- Chris

      parent reply	other threads:[~2003-07-02 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1057044203.11672.ezmlm@sources.redhat.com>
2003-07-01 15:36 ` Skeezics Boondoggle
2003-07-02  7:27   ` Hans Ronne
2003-07-02  8:01     ` Skeezics Boondoggle
2003-07-02 12:21       ` Hans Ronne
2003-07-02 17:50         ` Eric McDonald
2003-07-02 18:08         ` Skeezics Boondoggle [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=Pine.LNX.4.44.0307021051330.7849-100000@q7.q7.com \
    --to=skeezics@q7.com \
    --cc=hronne@telia.com \
    --cc=xconq7@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).