All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Christian Limpach <chris@pin.lu>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: NetBSD port and a couple of remarks
Date: Wed, 28 Jan 2004 09:05:44 -0800 (PST)	[thread overview]
Message-ID: <20040128090348.F70694@demos.bsdclusters.com> (raw)
In-Reply-To: <031301c3e5bb$05bfb240$070414ac@pin>

>
> yes, except that I don't want to deal with the bitkeeper licence and figure
> out whether I'm allowed to use it or not.
>
Are you doing development work on subversion, arch, or another revision
control system? If not, what is the concern?

			-Kip


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-01-28 17:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 20:59 NetBSD port and a couple of remarks Christian Limpach
2004-01-28  7:44 ` Kip Macy
2004-01-28  8:07 ` Ian Pratt
2004-01-28 14:54   ` Christian Limpach
2004-01-28 10:49 ` Steven Hand
2004-01-28 16:23   ` Christian Limpach
2004-01-28 16:38     ` Steven Hand
2004-01-28 16:51       ` Keir Fraser
2004-01-28 17:05     ` Kip Macy [this message]
2004-01-28 18:35       ` Christian Limpach
2004-01-28 19:03         ` Ian Pratt
2004-01-28 21:28           ` Kip Macy
2004-01-28 22:59             ` Andi Kleen
2004-01-28 23:10               ` Kip Macy
2004-01-28 23:24                 ` Andi Kleen
2004-01-28 23:48                   ` Kip Macy
2004-01-29  0:19                     ` Larry McVoy
2004-01-29  0:31                       ` Kip Macy
2004-01-29 11:14           ` John Szakmeister
2004-01-28 11:24 ` Ian Pratt
2004-01-28 17:07   ` Christian Limpach
2005-03-12 20:59 ` Thorsten Glaser

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=20040128090348.F70694@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=chris@pin.lu \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.