Commit d5484eb
committed
pack-objects: allow --shallow and --path-walk
There does not appear to be anything particularly incompatible about the
--shallow and --path-walk options of 'git pack-objects'. If shallow
commits are to be handled differently, then it is by the revision walk
that defines the commit set and which are interesting or uninteresting.
However, before the previous change, a trivial removal of the warning
would cause a failure in t5500-fetch-pack.sh when
GIT_TEST_PACK_PATH_WALK is enabled. The shallow fetch would provide more
objects than we desired, due to some incorrect behavior of the path-walk
API, especially around walking uninteresting objects.
The recently-added tests in t5538-push-shallow.sh help to confirm this
behavior is working with the --path-walk option if
GIT_TEST_PACK_PATH_WALK is enabled. These tests passed previously due to
the --path-walk feature being disabled in the presence of a shallow
clone.
Signed-off-by: Derrick Stolee <[email protected]>1 parent c45f35c commit d5484eb
1 file changed
+2
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
209 | 209 | | |
210 | 210 | | |
211 | 211 | | |
| 212 | + | |
212 | 213 | | |
213 | 214 | | |
214 | 215 | | |
| |||
4486 | 4487 | | |
4487 | 4488 | | |
4488 | 4489 | | |
| 4490 | + | |
4489 | 4491 | | |
4490 | 4492 | | |
4491 | 4493 | | |
| |||
4687 | 4689 | | |
4688 | 4690 | | |
4689 | 4691 | | |
4690 | | - | |
4691 | 4692 | | |
4692 | 4693 | | |
4693 | 4694 | | |
| |||
4875 | 4876 | | |
4876 | 4877 | | |
4877 | 4878 | | |
4878 | | - | |
4879 | | - | |
4880 | | - | |
4881 | | - | |
4882 | 4879 | | |
4883 | 4880 | | |
4884 | 4881 | | |
| |||
0 commit comments