From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Rahul Karnik <rahul@genebrew.com>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 from csv fails to compile
Date: Tue, 05 Aug 2003 11:02:38 +0900 [thread overview]
Message-ID: <3F2F103E.30800@tequila.co.jp> (raw)
In-Reply-To: <3F2EFE78.9000906@genebrew.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rahul Karnik wrote:
> Clemens Schwaighofer wrote:
>
>> I did, clean checkout (new directory), same error like before ...
>
>
> Can you diff against a current BK snapshot? This may be a problem with
> the BK->CVS gateway.
I would do immediatly if I would know how. I have installed bitkeeper
and I tried to do: bk pull bk://linux.bkbits.net/linux-2.5 but it just
gives me an error. I searched a bit, but I couldn't finde some helpful
help for how to checkout the tree from bk and at the moment I don't have
enough time to do so ...
would be a good thing to explain this in more detail on kernel.org eg
... perhaps directly on the main page ...
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/LxA9jBz/yQjBxz8RAt7HAKCVsoQey+dGURYUYxuPTET2mq9DmQCfQWFG
qftqIdFIP9pRCAuxCTnAU48=
=k+02
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-08-05 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 4:13 2.6.0 from csv fails to compile Clemens Schwaighofer
2003-08-04 6:43 ` Jens Axboe
2003-08-05 0:12 ` Clemens Schwaighofer
2003-08-05 0:46 ` Rahul Karnik
2003-08-05 2:02 ` Clemens Schwaighofer [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=3F2F103E.30800@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@genebrew.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 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.