public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "René 'Necoro' Neumann" <lists@necoro.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: bzr.eclass: The next level (this time with patch)
Date: Mon, 30 Mar 2009 23:53:36 +0200	[thread overview]
Message-ID: <49D13F60.2040909@necoro.eu> (raw)
In-Reply-To: <20090327014508.45d47afa@terra.solaris>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christian Faulhammer schrieb:
> Hi,
> 
> René 'Necoro' Neumann <lists@necoro.eu>:
>> So I'd vote for switching back to using normal checkouts (or branches
>> - they don't really differ in bzr for that matter).
> 
>  My tests with Bazaar 1.13.1 show roughly the same time with and
> without --lightweight.  Although I am not sure what you mean by
> export vs. fetch.

fetch: bzr branch / bzr co
export: bzr export

And depending on the type of the repository, the export will take
different times.

And I see the export as quite important, as the number of exports is at
least as high as the number of fetches.

Regards,
Necoro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknRP2AACgkQ4UOg/zhYFuBunwCfQG03AEruswY0UX39LTL6jmmt
ZWsAn06PRrCHaGMzoIneRVPLwzzYxrb2
=C9GU
-----END PGP SIGNATURE-----



      reply	other threads:[~2009-03-30 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  7:54 [gentoo-dev] bzr.eclass: The next level (this time with patch) Christian Faulhammer
2009-03-06 16:15 ` René 'Necoro' Neumann
2009-03-07 12:32   ` [gentoo-dev] " Christian Faulhammer
2009-03-11  0:46 ` [gentoo-dev] " René 'Necoro' Neumann
2009-03-11  0:54   ` René 'Necoro' Neumann
2009-03-27  0:45   ` [gentoo-dev] " Christian Faulhammer
2009-03-30 21:53     ` René 'Necoro' Neumann [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=49D13F60.2040909@necoro.eu \
    --to=lists@necoro.eu \
    --cc=gentoo-dev@lists.gentoo.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