From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Torri <storri@sbcglobal.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unable to grab 2.5 tree via bkbits
Date: Mon, 07 Jul 2003 17:46:52 -0400 [thread overview]
Message-ID: <3F09EA4C.2020405@pobox.com> (raw)
In-Reply-To: <1057613044.912.22.camel@base>
Stephen Torri wrote:
> On Mon, 2003-07-07 at 16:15, Jeff Garzik wrote:
>
>>Just to verify, I'm definitely able to pull and clone from
>>http://linux.bkbits.net/linux-2.5 ... I even cut-n-pasted your first
>>command line to be sure.
>>
>>It sounds like a local problem... disk space? no rights to write to curdir?
>
>
> Its a local problem. No write permissions set.
>
> Bitkeeper: Can you write the bk client to alert the user that it was
> unable to write to the local directory? It would help alert people to
> set things up properly.
You should direct this to support@bitmover.com ...
Jeff
prev parent reply other threads:[~2003-07-07 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 20:45 Unable to grab 2.5 tree via bkbits Stephen Torri
2003-07-07 21:15 ` Jeff Garzik
2003-07-07 21:24 ` Stephen Torri
2003-07-07 21:46 ` Jeff Garzik [this message]
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=3F09EA4C.2020405@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=storri@sbcglobal.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox