or my May 10 "Plans for post 0.8" message on the mailing
Aaron
Jeff Licquia wrote:
> Public bug reported:
>
> This is a wishlist bug. Filing on the recommendation of Jeff Bailey.
>
> We have lightweight checkouts, which depend entirely on access to the
> upstream branch, and heavy checkouts, which are fully independent and
> have full history. Would it be possible to have a hybrid checkout,
> which had some of the history locally, but not all of it?
>
> The idea is that the checkout would be "heavy" when dealing with
> "recent" commits (for some definition of "recent"), but would go into
> "light" mode when the user started working with commits beyond "recent".
> Most importantly, the user could work offline and commit just like a
> "heavy" checkout for the most common case, where the previous few
> revisions are all that the user cares about.
>
> Darcs has something like this: "darcs get --partial" only retrieves the
> most recent changesets.
>
> ** Affects: bzr (upstream)
> Severity: Normal
> Priority: (none set)
> Status: Unconfirmed
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This has already been proposed. See http:// bazaar- vcs.org/ HistoryHorizon
or my May 10 "Plans for post 0.8" message on the mailing
Aaron
Jeff Licquia wrote:
> Public bug reported:
>
> This is a wishlist bug. Filing on the recommendation of Jeff Bailey.
>
> We have lightweight checkouts, which depend entirely on access to the
> upstream branch, and heavy checkouts, which are fully independent and
> have full history. Would it be possible to have a hybrid checkout,
> which had some of the history locally, but not all of it?
>
> The idea is that the checkout would be "heavy" when dealing with
> "recent" commits (for some definition of "recent"), but would go into
> "light" mode when the user started working with commits beyond "recent".
> Most importantly, the user could work offline and commit just like a
> "heavy" checkout for the most common case, where the previous few
> revisions are all that the user cares about.
>
> Darcs has something like this: "darcs get --partial" only retrieves the
> most recent changesets.
>
> ** Affects: bzr (upstream)
> Severity: Normal
> Priority: (none set)
> Status: Unconfirmed
>
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org
nu1YWqI0RAoWMAJ 9yyjFdVN9zK6vzG 0tjVHbLiFlOrwCd GNn0 d4Gx4+MY=
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://
iD8DBQFEdat20F+
MNS95Ejs3ib1E4m
=bUXn
-----END PGP SIGNATURE-----