public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Larry McVoy <lm@work.bitmover.com>,
	bitkeeper-announce@work.bitmover.com,
	linux-kernel@vger.kernel.org
Subject: Re: bk-3.2.0 released
Date: Sat, 29 May 2004 15:20:18 +0200	[thread overview]
Message-ID: <20040529132018.GA6221@ucw.cz> (raw)
In-Reply-To: <20040529130436.GA20605@work.bitmover.com>

On Sat, May 29, 2004 at 06:04:36AM -0700, Larry McVoy wrote:
> On Sat, May 29, 2004 at 11:54:20AM +0200, Vojtech Pavlik wrote:
> > On Tue, May 18, 2004 at 04:32:38PM -0700, Larry McVoy wrote:
> > > BitKeeper Users,
> > > 
> > > BK/Pro 3.2.0 has been released and is in the BK download area,
> > > 
> > >     http://bitmover.com/download
> > 
> > Any chance of a native x86-64 version? 
> 
> We don't have any x86-64 machines but we could get one.  I asked about this
> a while back and people told me that there was no point, the x86 one worked
> perfectly.  Can you tell me what having a native one would gain?  If there
> is any gain we'll do it.

Well, yes, of course, the x86 version works just fine, because x86-64 is
backward compatible.

The benefits won't be huge:

	a marginal speed increase due to more registers
	no need for 32-bit libs on the system and in memory
	enough address space for bk, should it ever need more
	a general feeling of doing things right ;)	

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

      parent reply	other threads:[~2004-05-29 13:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 23:32 bk-3.2.0 released Larry McVoy
2004-05-19  6:51 ` Christoph Hellwig
2004-05-19 14:02   ` Larry McVoy
2004-05-19 14:11     ` Jan-Benedict Glaw
2004-05-19 14:16       ` Larry McVoy
2004-05-19 14:23         ` Kevin P. Fleming
2004-05-19 14:36           ` John Bradford
2004-05-19 18:47             ` Tomas Szepe
2004-05-19 14:26         ` Jan-Benedict Glaw
2004-05-19 14:48           ` Larry McVoy
2004-05-19 15:00             ` Jan-Benedict Glaw
2004-05-19 15:09               ` Larry McVoy
2004-05-19 16:10                 ` Nicolas Pitre
2004-05-19 20:06           ` Valdis.Kletnieks
2004-05-19 21:20             ` Stan Bubrouski
2004-05-19 14:33         ` Christoph Hellwig
2004-05-19 14:32     ` Christoph Hellwig
2004-05-19 14:34     ` John Bradford
2004-05-19 15:41   ` Bill Davidsen
2004-05-20  3:10   ` Jeff Sipek
2004-05-29  9:54 ` Vojtech Pavlik
2004-05-29 13:04   ` Larry McVoy
2004-05-29 13:15     ` Hugo Mills
2004-05-29 13:20       ` Larry McVoy
2004-05-29 15:47       ` Larry McVoy
2004-05-29 20:13         ` Bryan O'Sullivan
2004-05-30  3:59         ` David Lang
2004-05-29 13:20     ` Vojtech Pavlik [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=20040529132018.GA6221@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=bitkeeper-announce@work.bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@work.bitmover.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