public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: So let's get right to the point
Date: Fri, 21 Nov 2003 09:02:00 -0000	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDKECOGMAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311202146410.5296-100000@leon.phy.cmich.edu>

Eric McDonald wrote:
> Brandon Van Every wrote:
>
> > Sometimes I think you are used to working with a very
> > low class of people in hack3rz forums,
>
> Nope. You're about the lowest I've gone.

I see, Eric.  I'm not going to retract my apology to you, I've
apologized for what I should have.  But it's clear that you have never
been interested in moving on.  You basically don't accept the
differences of style between us.  That might change years from now, but
it won't change in any timeframe that matters to present ventures.

So let's get right to the point.  How many things that I propose, are
you going to obstruct out of your need for personal animosity?  I think
it's best that you make the list now.  That way, we don't have to waste
time with people talking about it, me implementing it, and you blocking
it.  State your turf, the things you certainly aren't going to give
ground on.

We'll make this partly a multiple choice test.

1. Python required in the kernel
a) yeah, that's awesome!
b) hell no.  Go away.

2. Kicking 7.5 out the door so that new features can be added
a) yeah, any week now!
b) I want my months before you even think about touching my source pool.

3. Recruiting a horde of Windows C# .NET developers
a) the more the merrier!
b) get out of here you Micro$quish suckup bastard

And, these are questions I expect firm answers to.  The number of (a)
answers determines whether Xconq is a good use of my time.


Cheers,                     www.indiegamedesign.com
Brandon Van Every           Seattle, WA

Taking risk where others will not.

  reply	other threads:[~2003-11-21  6:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  2:15 Xconq UI thoughts Stan Shebs
2003-11-20  2:26 ` Brandon J. Van Every
2003-11-20  2:57   ` Eric McDonald
2003-11-20  9:45     ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:49       ` Bruno Boettcher
2003-11-20 10:59         ` Brandon J. Van Every
2003-11-20 11:51           ` Jakob Ilves
2003-11-20 12:05             ` Brandon J. Van Every
2003-11-20 17:57             ` Jim Kingdon
2003-11-20 17:24       ` Eric McDonald
2003-11-20 17:51         ` Eric McDonald
2003-11-21  1:59         ` altruistic VS 2003 Solution files Brandon J. Van Every
2003-11-21  4:17           ` Eric McDonald
2003-11-21  9:02             ` Brandon J. Van Every [this message]
2003-11-21 23:14               ` So let's get right to the point Lincoln Peters
2003-11-22  0:06                 ` Why Eric doesn't like my personal style Brandon J. Van Every
2003-11-23 11:13                   ` Mark A. Flacy
2003-11-23 14:22                     ` Brandon J. Van Every
2003-11-22  0:07                 ` So let's get right to the point Brandon J. Van Every
2003-11-21  2:01         ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:31   ` Xconq UI thoughts Andreas Bringedal
2003-11-20 10:37     ` keys and menus Brandon J. Van Every
2003-11-20 10:58     ` Xconq UI thoughts Bruno Boettcher

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=OOEALCJCKEBJBIJHCNJDKECOGMAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.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).