hybrid checkout between lightweight and heavy aka history horizon

Bug #46561 reported by Jeff Licquia on 2006-05-25
60
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned
Nominated for Trunk by Tomasz Gajewski
Bazaar Subversion Plugin
Wishlist
Unassigned
Breezy
Medium
Jelmer Vernooij

Bug Description

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.

I think this is what's been discussed on the mailinglist as "history
horizons". Where a branch (bound or not bound) only have a part of the
history.

I too, really would like this, but mostly for unbound branches.

/Erik

tor 2006-05-25 klockan 12:29 +0000 skrev Jeff Licquia:

> 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
>

Aaron Bentley (abentley) wrote :

-----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-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEdat20F+nu1YWqI0RAoWMAJ9yyjFdVN9zK6vzG0tjVHbLiFlOrwCdGNn0
MNS95Ejs3ib1E4md4Gx4+MY=
=bUXn
-----END PGP SIGNATURE-----

On Thu, 2006-05-25 at 13:04 +0000, Aaron Bentley wrote:
> This has already been proposed. See http://bazaar-
> vcs.org/HistoryHorizon

Yup, that looks exactly like it. Sorry to bother you all. Feel free to
close the bug.

On 25 May 2006, Jeff Licquia <email address hidden> wrote:
> On Thu, 2006-05-25 at 13:04 +0000, Aaron Bentley wrote:
> > This has already been proposed. See http://bazaar-
> > vcs.org/HistoryHorizon
>
> Yup, that looks exactly like it. Sorry to bother you all. Feel free to
> close the bug.

Even though there's a spec I think there's no existing bug issue for it,
so let's leave it open as wishlist.

Thanks Jeff
--
Martin

Marking this as a wishlist item, and associating it with a spec.

Changed in bzr:
importance: Medium → Wishlist
status: Unconfirmed → Confirmed
Václav Šmilauer (eudoxos) wrote :

Any progress on this front? Couldn't google anything up.

Jelmer Vernooij (jelmer) on 2011-02-01
Changed in bzr-svn:
status: New → Triaged
importance: Undecided → Wishlist
Jelmer Vernooij (jelmer) on 2011-03-10
Changed in bzr-svn:
status: Triaged → Invalid
Samuel Bronson (naesten) wrote :

Ping?

Jeff Licquia (jeff-licquia) wrote :

No progress, as far as I can tell. The wiki page is still there (moved to http://wiki.bazaar.canonical.com/HistoryHorizon as part of the general migration off bazaar-vcs.org). Links from there to the Launchpad blueprint still work (https://launchpad.net/bzr/+spec/shallow-checkouts).

Martin Pool (mbp) on 2011-04-11
Changed in bzr:
importance: Wishlist → Medium
tags: added: feature
summary: - hybrid checkout between lightweight and heavy
+ hybrid checkout between lightweight and heavy aka history horizon
Jelmer Vernooij (jelmer) on 2017-11-08
tags: added: check-for-breezy
Jelmer Vernooij (jelmer) on 2018-02-09
Changed in brz:
importance: Undecided → Medium
status: New → Triaged
Jelmer Vernooij (jelmer) on 2018-02-20
tags: removed: check-for-breezy
Jelmer Vernooij (jelmer) on 2018-11-11
Changed in brz:
milestone: none → 3.0.0
status: Triaged → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers