hybrid checkout between lightweight and heavy aka history horizon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bazaar Subversion Plugin |
Invalid
|
Wishlist
|
Unassigned | ||
Breezy |
In Progress
|
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.
Changed in bzr-svn: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in bzr-svn: | |
status: | Triaged → Invalid |
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 |
tags: | added: check-for-breezy |
Changed in brz: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | removed: check-for-breezy |
Changed in brz: | |
milestone: | none → 3.0.0 |
status: | Triaged → In Progress |
assignee: | nobody → Jelmer Vernooij (jelmer) |
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
>