public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dan Davis" <davis.37@osu.edu>
To: <opensource-admin@cis.ohio-state.edu>, <bernstein.46@osu.edu>,
	<jjasen1@umbc.edu>
Cc: <lm@bitmover.com>, <kentborg@borg.org>,
	<opensource@cis.ohio-state.edu>, <hozer@drgw.net>, <pavel@ucw.cz>,
	<linux-kernel@vger.kernel.org>, <akpm@zip.com.au>
Subject: Re: [opensource] Re: Petition Against Official Endorsement ofBitKeeper by Linux Maintainers
Date: Thu, 07 Mar 2002 17:17:41 -0500	[thread overview]
Message-ID: <sc87a0cc.012@pf.ueo.ohio-state.edu> (raw)

To all who read this list.  I respect someone's ideology and I respect
a person's need to support his family.  I like Opensource, Linux, etc.,
but I have to work in a Microsoft world at this "present time" 
to support my family.  I have learned to respect people's right to disagree.  
Not everyone will agree with the other's conclusions and there have 
been a number of good points raised on both sides.  Please pause 
and consider them.  If you must disagree, please do it in a respectful 
and business like manner.  When you don't, you are only damaging 
your own argument.  Thanks.


Dan Davis, Sys Dev/Eng, CNA
Physical Facilities
Ohio State University
614-688-3271  Work
614-292-6751  Fax
davis.37@osu.edu

"Preparation creates confidence.  
Process leads to sound execution.  
Regimen aims effort toward perfection.  
Excellence matters."  Orel Hershiser

>>> John Jasen <jjasen1@umbc.edu> 03/07/02 05:01PM >>>
On Thu, 7 Mar 2002, michael bernstein wrote:

> Get over the money issue though.  There are a lot of
> people who could benefit from bitkeeper being opensourced, so why not go
> and do it?

rent. food. clothing. basic necessities and whatnot.

Just a thought.

> Serve others, not yourself.

I begin to smell the exuberance of youthful ideology.

Does anyone have a can of Lysol I can borrow?

BK belongs to bitmover. They can do whatever they want with it. Deal.

--
-- John E. Jasen (jjasen1@umbc.edu)
-- In theory, theory and practise are the same. In practise, they aren't.

_______________________________________________
Opensource mailing list
Opensource@mail.cis.ohio-state.edu 
http://mail.cis.ohio-state.edu/mailman/listinfo/opensource


             reply	other threads:[~2002-03-07 22:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 22:17 Dan Davis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-05 21:52 Petition Against Official Endorsement of BitKeeper by Linux Maintainers The Open Source Club at The Ohio State University
2002-03-05 22:41 ` Jeff V. Merkey
2002-03-05 22:40   ` [opensource] " Colin Walters
2002-03-05 22:54     ` [opensource] Re: Petition Against Official Endorsement ofBitKeeper " Jeff Garzik
2002-03-05 23:06       ` Colin Walters
2002-03-05 23:11       ` William Lee Irwin III
2002-03-06  0:09       ` Jeff V. Merkey
2002-03-06  2:23       ` Karl
2002-03-06  3:35         ` michael bernstein
2002-03-07  1:22       ` David Schwartz

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=sc87a0cc.012@pf.ueo.ohio-state.edu \
    --to=davis.37@osu.edu \
    --cc=akpm@zip.com.au \
    --cc=bernstein.46@osu.edu \
    --cc=hozer@drgw.net \
    --cc=jjasen1@umbc.edu \
    --cc=kentborg@borg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=opensource-admin@cis.ohio-state.edu \
    --cc=opensource@cis.ohio-state.edu \
    --cc=pavel@ucw.cz \
    /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