From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Matt_Domsch@Dell.com, davej@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH 2.5.x] move asm-ia64/efi.h to linux/efi.h
Date: Sat, 17 Aug 2002 11:44:53 -0700 [thread overview]
Message-ID: <20020817114453.D27790@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208171131400.3169-100000@home.transmeta.com>; from torvalds@transmeta.com on Sat, Aug 17, 2002 at 11:32:49AM -0700
> > Linus, please apply
> > http://domsch.com/linux/patches/ia64/linux-2.5-efihmove.cset
>
> Oh, wow. I thought csets in the email were inconvenient, but cset's on
> web-sites take the price.
>
> Please make it a full BK tree to pull from instead, or just include them
> in the email.
This is starting to be a FAQ so...
The way Linus wants to work with BK is to have a BK tree from which he
can pull when he is ready to accept those changes. You can set up a
tree at your site if they haven't firewalled everything or you can set
one up on bkbits.net.
The main reason bkbits.net exists is because lots of commercial companies
don't want to have any open ports so there isn't an easy way to make
your tree available. Since BK works over http there is an easy way for
you to get in/out from the inside but outsiders are stuck.
Go www.bitkeeper.com and click on Hosted Projects, it will tell you how
to set one up. Let me know if you have problems/questions.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-08-17 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 18:10 [BK PATCH 2.5.x] move asm-ia64/efi.h to linux/efi.h Matt_Domsch
2002-08-17 18:32 ` Linus Torvalds
2002-08-17 18:44 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-17 22:13 Matt_Domsch
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=20020817114453.D27790@work.bitmover.com \
--to=lm@bitmover.com \
--cc=Matt_Domsch@Dell.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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