way to limit number of revisions processed during fetch
Bug #750175 reported by
Jelmer Vernooij
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Jelmer Vernooij | ||
Bazaar Git Plugin |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
Bazaar Hg Plugin |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
Bazaar Subversion Plugin |
Fix Released
|
Medium
|
Jelmer Vernooij |
Bug Description
bzr-svn/
Previously this code worked using a hack that assumed the last revision fetched was the tip of the branch if all revisions were fetched. Now that tags are being fetched this is no longer true.
It would be nice to have this sort of infrastructure in Bazaar itself, perhaps using a limit= argument to Repository.fetch()
Related branches
lp:~jelmer/bzr/fetch-limit
- Andrew Bennetts: Approve
- John A Meinel: Pending requested
-
Diff: 468 lines (+144/-37)11 files modifiedbzrlib/branch.py (+7/-4)
bzrlib/fetch.py (+22/-13)
bzrlib/graph.py (+10/-5)
bzrlib/plugins/weave_fmt/repository.py (+7/-1)
bzrlib/remote.py (+3/-2)
bzrlib/repofmt/knitrepo.py (+7/-1)
bzrlib/repository.py (+8/-3)
bzrlib/tests/per_interbranch/test_fetch.py (+49/-1)
bzrlib/tests/per_interrepository/test_interrepository.py (+11/-0)
bzrlib/vf_repository.py (+17/-7)
doc/en/release-notes/bzr-2.4.txt (+3/-0)
Changed in bzr: | |
importance: | Medium → High |
status: | Triaged → Confirmed |
Changed in bzr: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Confirmed → In Progress |
Changed in bzr-git: | |
status: | New → In Progress |
Changed in bzr-hg: | |
status: | New → In Progress |
Changed in bzr-svn: | |
status: | New → In Progress |
Changed in bzr-git: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in bzr-hg: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in bzr-svn: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in bzr-git: | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
milestone: | none → 0.6.1 |
Changed in bzr-svn: | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
milestone: | none → 1.1.0 |
Changed in bzr-hg: | |
status: | In Progress → Fix Committed |
importance: | Undecided → Medium |
milestone: | none → 0.2 |
Changed in bzr: | |
milestone: | none → 2.4b3 |
status: | In Progress → Fix Released |
Changed in bzr-git: | |
status: | Fix Committed → Fix Released |
Changed in bzr-svn: | |
status: | Fix Committed → Fix Released |
Changed in bzr-hg: | |
status: | Fix Committed → Fix Released |
milestone: | 0.2 → 0.1.1 |
To post a comment you must log in.
I guess if you're looking at this again, I'd say that what the code importers really care about is to limit the _time_ spent processing revisions during fetch. This might even be useful for people who are pulling large branches over low-bandwidth links, rather than running bzr pull -r 1000; bzr pull -r 2000; and so on, but that's perhaps going off into lala land.
Yay for fixing this problem without hacks though.