From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: xconq net game: loss of sync
Date: Sun, 29 Aug 2004 13:15:00 -0000 [thread overview]
Message-ID: <41314A14.1040306@phy.cmich.edu> (raw)
In-Reply-To: <200408290307.i7T37AA01871@panix5.panix.com>
Jim Kingdon wrote:
> Oh, a bug in the supply code is sort of what I was insinuating before,
It could also be due to the fact you guys may not have saved at exactly
the same point, and some automatic things (plan executions) continued
even after you got out sync, and thus some parts of the game diffs are
present for that reason.
> but there is at least one other possibility: whether I really ended up
> with the same version of xconq as Tom. I did a CVS update and applied
> Eric's patch ( http://sources.redhat.com/ml/xconq7/2004/msg01014.html
> ). So assuming that is what Eric did, this probably isn't it.
This is exactly what I did before building the Windows executables.
>Insert groveling about how I shouldn't really gumble
> so much unless I'm volunteering to fix it).
;-)
Eric
next prev parent reply other threads:[~2004-08-29 3:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 0:54 Net Game Showstopper tsbvc
2004-08-29 0:55 ` Eric McDonald
2004-08-29 1:09 ` Robert Goulding
2004-08-29 1:35 ` We Need a Forum Elijah Meeks
2004-08-29 1:40 ` mskala
2004-08-29 1:43 ` Net Game Showstopper Eric McDonald
2004-08-29 1:57 ` Lincoln Peters
2004-08-29 2:04 ` mskala
2004-08-29 2:53 ` Eric McDonald
2004-08-29 15:59 ` Robert Goulding
2004-08-29 3:07 ` Jim Kingdon
2004-08-29 3:14 ` xconq net game: loss of sync Jim Kingdon
2004-08-29 13:15 ` Eric McDonald [this message]
2004-08-29 19:17 ` Net Game Showstopper Eric McDonald
2004-08-29 2:57 xconq net game: loss of sync Jim Kingdon
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=41314A14.1040306@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=kingdon@panix.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).