From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Do I have to buy a license to use BK for kernel development?
Date: Wed, 10 Sep 2003 16:11:18 +1200 [thread overview]
Message-ID: <1063167031.3399.7.camel@laptop-linux> (raw)
Hi all.
I've made one or two attempts at beginning to use BK for my kernel
development work, but each time I've been stuck by the licensing code. I
use it for a little while, and then get a message about not being
allowed to commit because of logging (or something to that effect). Can
someone give me info on how to set up BK so that you don't get these
issues? (I'm assuming I don't need to buy it to use it for kernel
development). I should add that I'm doing 99% of my work disconnected
from the internet.
Can I also suggest that info on this be added to Documentation/BK-Usage?
Thanks in advance and regards,
Nigel
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
-- Romans 5:6, NIV.
next reply other threads:[~2003-09-10 4:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 4:11 Nigel Cunningham [this message]
2003-09-10 4:59 ` Do I have to buy a license to use BK for kernel development? Larry McVoy
2003-09-10 5:18 ` Nigel Cunningham
2003-10-11 11:02 ` Matthias Urlichs
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=1063167031.3399.7.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=linux-kernel@vger.kernel.org \
/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