What's cooking (2017/12 #01)
Junio C Hamano committed
Dec 4, 2017 at 13:45 UTC
77d249b13baf3c0d6bf6a16c5519072f9e0ad08e
1 file changed
+142
-236
whats-cooking.txt
+142
-236
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Nov 2017, #08; Tue, 28)
3
+Subject: What's cooking in git.git (Dec 2017, #01; Mon, 4)
4
X-master-at: 1a4e40aa5dc16564af879142ba9dfbbb88d1e5ff
5
-X-next-at: 9478a6608122bc94547963754b0a9f2821bb2cfb
5
+X-next-at: 49b39d22972bb18690a282774c8bc54bea6b63b7
6
7
-What's cooking in git.git (Nov 2017, #08; Tue, 28)
7
+What's cooking in git.git (Dec 2017, #01; Mon, 4)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking. Commits prefixed with
@@ -12,186 +12,173 @@ Here are the topics that have been cooking. Commits prefixed with
12
'+' are in 'next'. The ones marked with '.' do not appear in any of
13
the integration branches, but I am still holding onto them.
14
15
-Git 2.15.1 has been tagged, with many of the fixes that have already
16
-been in 'master'.
17
-
15
You can find the changes described here in the integration branches
16
of the repositories listed at
17
18
http://git-blame.blogspot.com/p/git-public-repositories.html
19
20
--------------------------------------------------
24
-[Graduated to "master"]
25
-
26
-* ew/rebase-mboxrd (2017-11-18) 1 commit
27
- (merged to 'next' on 2017-11-21 at 88eaaac334)
28
- + rebase: use mboxrd format to avoid split errors
29
-
30
- When "git rebase" prepared an mailbox of changes and fed it to "git
31
- am" to replay them, it was confused when a stray "From " happened
32
- to be in the log message of one of the replayed changes. This has
33
- been corrected.
34
-
35
-
36
-* jc/branch-name-sanity (2017-11-15) 4 commits
37
- (merged to 'next' on 2017-11-20 at 7236b0dde3)
38
- + builtin/branch: remove redundant check for HEAD
39
- + branch: correctly reject refs/heads/{-dash,HEAD}
40
- + branch: split validate_new_branchname() into two
41
- + branch: streamline "attr_only" handling in validate_new_branchname()
42
-
43
- "git branch" and "git checkout -b" are now forbidden from creating
44
- a branch whose name is "HEAD".
21
+[New Topics]
22
23
+* ab/simplify-perl-makefile (2017-12-04) 1 commit
24
+ - Makefile: replace perl/Makefile.PL with simple make rules
25
47
-* jc/ignore-cr-at-eol (2017-11-08) 2 commits
48
- (merged to 'next' on 2017-11-20 at 9f7bae7cbd)
49
- + diff: --ignore-cr-at-eol
50
- + xdiff: reassign xpparm_t.flags bits
26
+ The build procedure for perl/ part has been greatly simplified by
27
+ weaning ourselves off of MakeMaker.
28
52
- The "diff" family of commands learned to ignore differences in
53
- carriage return at the end of line.
29
30
+* cc/object-filtering-typofix (2017-12-04) 1 commit
31
+ - list-objects-filter-options: fix 'keword' typo in comment
32
+ (this branch uses jh/object-filtering; is tangled with jh/fsck-promisors and jh/partial-clone.)
33
56
-* jc/merge-base-fork-point-doc (2017-11-09) 1 commit
57
- (merged to 'next' on 2017-11-20 at 199b9255b4)
58
- + merge-base --fork-point doc: clarify the example and failure modes
34
+ Typofix for a topic already in 'next'.
35
60
- Clarify and enhance documentation for "merge-base --fork-point", as
61
- it was clear what it computed but not why/what for.
36
+ JeffH said that jh/object-filtering needs further polishing a bit
37
+ before graduating to 'master', so it would be appreciated if this
38
+ can also be rolled into such an incremental update.
39
40
64
-* ks/rebase-no-git-foo (2017-11-21) 1 commit
65
- (merged to 'next' on 2017-11-22 at 336552dbb7)
66
- + git-rebase: clean up dashed-usages in messages
41
+* cc/skip-to-optional-val (2017-12-04) 4 commits
42
+ - diff: use skip_to_optional_val_default()
43
+ - diff: use skip_to_optional_val()
44
+ - index-pack: use skip_to_optional_val()
45
+ - git-compat-util: introduce skip_to_optional_val()
46
68
- Mentions of "git-rebase" and "git-am" (dashed form) still remained
69
- in end-user visible strings emitted by the "git rebase" command;
70
- they have been corrected.
47
+ Introduce a helper to simplify code to parse a common pattern that
48
+ expects either "--key" or "--key=<something>".
49
50
+ This may want a final reroll to make it harder to misuse by
51
+ allowing NULL at the valp part of the argument.
52
+ cf. <xmqqh8t6o9me.fsf@gitster.mtv.corp.google.com>
53
+ cf. <xmqqd13uo9d1.fsf@gitster.mtv.corp.google.com>
54
73
-* ma/branch-list-paginate (2017-11-20) 3 commits
74
- (merged to 'next' on 2017-11-22 at eecd7f2369)
75
- + branch: change default of `pager.branch` to "on"
76
- + branch: respect `pager.branch` in list-mode only
77
- + t7006: add tests for how git branch paginates
55
79
- "git branch --list" learned to show its output through the pager by
80
- default when the output is going to a terminal, which is controlled
81
- by the pager.branch configuration variable. This is similar to a
82
- recent change to "git tag --list".
56
+* lb/rebase-i-short-command-names (2017-12-04) 9 commits
57
+ - t3404: add test case for abbreviated commands
58
+ - rebase -i: learn to abbreviate command names
59
+ - rebase -i -x: add exec commands via the rebase--helper
60
+ - rebase -i: update functions to use a flags parameter
61
+ - rebase -i: replace reference to sha1 with oid
62
+ - rebase -i: refactor transform_todo_ids
63
+ - rebase -i: set commit to null in exec commands
64
+ - Documentation: use preferred name for the 'todo list' script
65
+ - Documentation: move rebase.* configs to new file
66
67
+ Allow a single-letter command name in the "rebase -i" todo list.
68
85
-* pw/sequencer-recover-from-unlockable-index (2017-11-16) 1 commit
86
- (merged to 'next' on 2017-11-20 at 36f0ed26ce)
87
- + sequencer: reschedule pick if index can't be locked
69
+ This may want a final reroll to avoid adding new reference to insn
70
+ where todo is the more modern term, among other minor things.
71
+ cf. <xmqq4lp6o4p4.fsf@gitster.mtv.corp.google.com>
72
89
- The sequencer machinery (used by "git cherry-pick A..B", and "git
90
- rebase -i", among other things) would have lost a commit if stopped
91
- due to an unlockable index file, which has been fixed.
73
74
+* ra/prompt-eread-fix (2017-12-04) 2 commits
75
+ - git-prompt: fix reading files with windows line endings
76
+ - git-prompt: make __git_eread intended use explicit
77
94
-* rs/apply-inaccurate-eof-with-incomplete-line (2017-11-17) 1 commit
95
- (merged to 'next' on 2017-11-20 at c8aee1d135)
96
- + apply: update line lengths for --inaccurate-eof
78
+ Update the shell prompt script (in contrib/) to strip trailing CR
79
+ from strings read from various "state" files.
80
98
- "git apply --inaccurate-eof" when used with "--ignore-space-change"
99
- triggered an internal sanity check, which has been fixed.
81
+ Proposed log messages of both commits may need small fixes.
82
+ cf. <xmqqindmml25.fsf@gitster.mtv.corp.google.com>
83
+ cf. <alpine.DEB.2.21.1.1712041516280.98586@virtualbox>
84
85
102
-* rs/config-write-section-fix (2017-11-18) 1 commit
103
- (merged to 'next' on 2017-11-21 at a7f3f93e0c)
104
- + config: flip return value of write_section()
86
+* ds/for-each-file-in-obj-micro-optim (2017-12-04) 1 commit
87
+ - sha1_file: use strbuf_add() instead of strbuf_addf()
88
106
- There was a recent semantic mismerge in the codepath to write out a
107
- section of a configuration section, which has been corrected.
89
+ The code to iterate over loose object files got optimized.
90
91
+ Will merge to 'next'.
92
110
-* rs/include-comments-before-the-function-header (2017-11-21) 6 commits
111
- (merged to 'next' on 2017-11-22 at d7255a836f)
112
- + grep: show non-empty lines before functions with -W
113
- + grep: update boundary variable for pre-context
114
- + t7810: improve check of -W with user-defined function lines
115
- + xdiff: show non-empty lines before functions with -W
116
- + xdiff: factor out is_func_rec()
117
- + t4051: add test for comments preceding function lines
93
+--------------------------------------------------
94
+[Stalled]
95
119
- "git grep -W", "git diff -W" and their friends learned a heuristic
120
- to extend a pre-context beyond the line that matches the "function
121
- pattern" (aka "diff.*.xfuncname") to include a comment block, if
122
- exists, that immediately precedes it.
96
+* jc/merge-symlink-ours-theirs (2017-09-26) 1 commit
97
+ - merge: teach -Xours/-Xtheirs to symbolic link merge
98
99
+ "git merge -Xours/-Xtheirs" learned to use our/their version when
100
+ resolving a conflicting updates to a symbolic link.
101
125
-* rv/sendemail-tocmd-in-config-and-completion (2017-11-14) 2 commits
126
- (merged to 'next' on 2017-11-20 at 75cf6e2fc3)
127
- + completion: add git config sendemail.tocmd
128
- + Documentation/config: add sendemail.tocmd to list preceding "See git-send-email(1)"
102
+ Needs review.
103
130
- Teach "sendemail.tocmd" to places that know about "sendemail.to",
131
- like documentation and shell completion (in contrib/).
104
105
+* mg/merge-base-fork-point (2017-09-17) 3 commits
106
+ - merge-base: find fork-point outside partial reflog
107
+ - merge-base: return fork-point outside reflog
108
+ - t6010: test actual test output
109
134
-* sb/test-cherry-pick-submodule-getting-in-a-way (2017-11-15) 2 commits
135
- (merged to 'next' on 2017-11-20 at fe7016689e)
136
- + merge-recursive: handle addition of submodule on our side of history
137
- + t/3512: demonstrate unrelated submodule/file conflict as cherry-pick failure
110
+ "merge-base --fork-point $branch $commit" is used to guess on which
111
+ commit among the commits that were once at the tip of the $branch the
112
+ $commit was built on top of, and it learns these historical tips from
113
+ the reflog of the $branch. When the true fork-point is lost due to
114
+ pruning of old reflog entries, the command does not give any output,
115
+ because it has no way to guess correctly and does not want to mislead
116
+ the user with a wrong guess.
117
139
- The three-way merge performed by "git cherry-pick" was confused
140
- when a new submodule was added in the meantime, which has been
141
- fixed (or "papered over").
118
+ The command has been updated to give the best but not known to be
119
+ correct guess, based on a hope that a merge-base between $commit and a
120
+ virtual merge across all the reflog entries that still are available
121
+ for $branch may still be a closer to the true fork-point than the
122
+ merge-base between $commit and the current tip of the $branch.
123
124
+ This may have to be offered by an additional option, to allow the
125
+ users that are prepared to see a potentially incorrect guess to opt
126
+ into the feature, without affecting the current callers that may not
127
+ be prepared to accept a guess that is not known to be correct.
128
144
-* sd/branch-copy (2017-11-16) 1 commit
145
- (merged to 'next' on 2017-11-20 at e33bcc460a)
146
- + config: avoid "write_in_full(fd, buf, len) != len" pattern
129
+ What's the doneness of this one?
130
148
- Code clean-up.
131
132
+* jk/drop-ancient-curl (2017-08-09) 5 commits
133
+ - http: #error on too-old curl
134
+ - curl: remove ifdef'd code never used with curl >=7.19.4
135
+ - http: drop support for curl < 7.19.4
136
+ - http: drop support for curl < 7.16.0
137
+ - http: drop support for curl < 7.11.1
138
151
-* sw/pull-ipv46-passthru (2017-11-21) 1 commit
152
- (merged to 'next' on 2017-11-22 at b06021eeba)
153
- + pull: pass -4/-6 option to 'git fetch'
139
+ Some code in http.c that has bitrot is being removed.
140
155
- Contrary to the documentation, "git pull -4/-6 other-args" did not
156
- ask the underlying "git fetch" to go over IPv4/IPv6, which has been
157
- corrected.
141
+ Expecting a reroll.
142
143
160
-* tb/add-renormalize (2017-11-17) 1 commit
161
- (merged to 'next' on 2017-11-20 at e302f3591f)
162
- + add: introduce "--renormalize"
144
+* mk/use-size-t-in-zlib (2017-08-10) 1 commit
145
+ . zlib.c: use size_t for size
146
164
- "git add --renormalize ." is a new and safer way to record the fact
165
- that you are correcting the end-of-line convention and other
166
- "convert_to_git()" glitches in the in-repository data.
147
+ The wrapper to call into zlib followed our long tradition to use
148
+ "unsigned long" for sizes of regions in memory, which have been
149
+ updated to use "size_t".
150
151
+ Needs resurrecting by making sure the fix is good and still applies
152
+ (or adjusted to today's codebase).
153
169
-* tz/complete-branch-copy (2017-11-17) 1 commit
170
- (merged to 'next' on 2017-11-20 at 6d22384fcd)
171
- + completion: add '--copy' option to 'git branch'
154
173
- Command line completion (in contrib/) has been taught about the
174
- "--copy" option of "git branch".
155
+* mg/status-in-progress-info (2017-05-10) 2 commits
156
+ - status --short --inprogress: spell it as --in-progress
157
+ - status: show in-progress info for short status
158
159
+ "git status" learns an option to report various operations
160
+ (e.g. "merging") that the user is in the middle of.
161
177
-* tz/notes-error-to-stderr (2017-11-15) 1 commit
178
- (merged to 'next' on 2017-11-20 at a45d441ee2)
179
- + notes: send "Automatic notes merge failed" messages to stderr
162
+ cf. <xmqqmvakcdqw.fsf@gitster.mtv.corp.google.com>
163
181
- "git notes" sent its error message to its standard output stream,
182
- which was corrected.
164
165
+* nd/worktree-move (2017-04-20) 6 commits
166
+ - worktree remove: new command
167
+ - worktree move: refuse to move worktrees with submodules
168
+ - worktree move: accept destination as directory
169
+ - worktree move: new command
170
+ - worktree.c: add update_worktree_location()
171
+ - worktree.c: add validate_worktree()
172
185
-* tz/redirect-fix (2017-11-14) 2 commits
186
- (merged to 'next' on 2017-11-20 at 5b13f7026e)
187
- + rebase: fix stderr redirect in apply_autostash()
188
- + t/lib-gpg: fix gpgconf stderr redirect to /dev/null
173
+ "git worktree" learned move and remove subcommands.
174
190
- A few scripts (both in production and tests) incorrectly redirected
191
- their error output. These have been corrected.
175
+ Expecting a reroll.
176
+ cf. <20170420101024.7593-1-pclouds@gmail.com>
177
+ cf. <20170421145916.mknekgqzhxffu7di@sigill.intra.peff.net>
178
+ cf. <d0e81b1e-5869-299e-f462-4d43dc997bd1@ramsayjones.plus.com>
179
180
--------------------------------------------------
194
-[New Topics]
181
+[Cooking]
182
183
* en/merge-recursive-icase-removal (2017-11-27) 1 commit
184
- merge-recursive: ignore_case shouldn't reject intentional removals
@@ -239,7 +226,8 @@ of the repositories listed at
226
Will merge to 'next'.
227
228
242
-* cc/require-tcl-tk-for-build (2017-11-27) 1 commit
229
+* cc/require-tcl-tk-for-build (2017-11-29) 2 commits
230
+ - travis-ci: avoid new tcl/tk build requirement
231
- Makefile: check that tcl/tk is installed
232
233
A first-time builder of Git may have installed neither tclsh nor
@@ -300,95 +288,6 @@ of the repositories listed at
288
289
Will merge to 'next'.
290
303
---------------------------------------------------
304
-[Stalled]
305
-
306
-* jc/merge-symlink-ours-theirs (2017-09-26) 1 commit
307
- - merge: teach -Xours/-Xtheirs to symbolic link merge
308
-
309
- "git merge -Xours/-Xtheirs" learned to use our/their version when
310
- resolving a conflicting updates to a symbolic link.
311
-
312
- Needs review.
313
-
314
-
315
-* mg/merge-base-fork-point (2017-09-17) 3 commits
316
- - merge-base: find fork-point outside partial reflog
317
- - merge-base: return fork-point outside reflog
318
- - t6010: test actual test output
319
-
320
- "merge-base --fork-point $branch $commit" is used to guess on which
321
- commit among the commits that were once at the tip of the $branch the
322
- $commit was built on top of, and it learns these historical tips from
323
- the reflog of the $branch. When the true fork-point is lost due to
324
- pruning of old reflog entries, the command does not give any output,
325
- because it has no way to guess correctly and does not want to mislead
326
- the user with a wrong guess.
327
-
328
- The command has been updated to give the best but not known to be
329
- correct guess, based on a hope that a merge-base between $commit and a
330
- virtual merge across all the reflog entries that still are available
331
- for $branch may still be a closer to the true fork-point than the
332
- merge-base between $commit and the current tip of the $branch.
333
-
334
- This may have to be offered by an additional option, to allow the
335
- users that are prepared to see a potentially incorrect guess to opt
336
- into the feature, without affecting the current callers that may not
337
- be prepared to accept a guess that is not known to be correct.
338
-
339
- What's the doneness of this one?
340
-
341
-
342
-* jk/drop-ancient-curl (2017-08-09) 5 commits
343
- - http: #error on too-old curl
344
- - curl: remove ifdef'd code never used with curl >=7.19.4
345
- - http: drop support for curl < 7.19.4
346
- - http: drop support for curl < 7.16.0
347
- - http: drop support for curl < 7.11.1
348
-
349
- Some code in http.c that has bitrot is being removed.
350
-
351
- Expecting a reroll.
352
-
353
-
354
-* mk/use-size-t-in-zlib (2017-08-10) 1 commit
355
- . zlib.c: use size_t for size
356
-
357
- The wrapper to call into zlib followed our long tradition to use
358
- "unsigned long" for sizes of regions in memory, which have been
359
- updated to use "size_t".
360
-
361
- Needs resurrecting by making sure the fix is good and still applies
362
- (or adjusted to today's codebase).
363
-
364
-
365
-* mg/status-in-progress-info (2017-05-10) 2 commits
366
- - status --short --inprogress: spell it as --in-progress
367
- - status: show in-progress info for short status
368
-
369
- "git status" learns an option to report various operations
370
- (e.g. "merging") that the user is in the middle of.
371
-
372
- cf. <xmqqmvakcdqw.fsf@gitster.mtv.corp.google.com>
373
-
374
-
375
-* nd/worktree-move (2017-04-20) 6 commits
376
- - worktree remove: new command
377
- - worktree move: refuse to move worktrees with submodules
378
- - worktree move: accept destination as directory
379
- - worktree move: new command
380
- - worktree.c: add update_worktree_location()
381
- - worktree.c: add validate_worktree()
382
-
383
- "git worktree" learned move and remove subcommands.
384
-
385
- Expecting a reroll.
386
- cf. <20170420101024.7593-1-pclouds@gmail.com>
387
- cf. <20170421145916.mknekgqzhxffu7di@sigill.intra.peff.net>
388
- cf. <d0e81b1e-5869-299e-f462-4d43dc997bd1@ramsayjones.plus.com>
389
-
390
---------------------------------------------------
391
-[Cooking]
291
292
* en/rename-directory-detection (2017-11-21) 33 commits
293
- merge-recursive: ensure we write updates for directory-renamed file
@@ -672,28 +571,31 @@ of the repositories listed at
571
572
573
* dj/runtime-prefix (2017-11-28) 4 commits
675
- - exec_cmd: RUNTIME_PREFIX on some POSIX systems
676
- - Makefile: add Perl runtime prefix support
677
- - Makefile: add support for "perllibdir"
678
- - Makefile: generate Perl header from template file
574
+ . exec_cmd: RUNTIME_PREFIX on some POSIX systems
575
+ . Makefile: add Perl runtime prefix support
576
+ . Makefile: add support for "perllibdir"
577
+ . Makefile: generate Perl header from template file
578
579
A build-time option has been added to allow Git to be told to refer
580
to its associated files relative to the main binary, in the same
581
way that has been possible on Windows for quite some time, for
582
Linux, BSDs and Darwin.
583
685
- Will merge to 'next'.
584
+ Tentatively kicked out of 'next' to see how well another topic
585
+ ab/simplify-perl-makefile that heavily conflicts with this fares.
586
587
688
-* jc/editor-waiting-message (2017-11-17) 1 commit
588
+* ls/editor-waiting-message (2017-12-04) 2 commits
589
- launch_editor(): indicate that Git waits for user input
590
+ - refactor "dumb" terminal determination
591
592
Git shows a message to tell the user that it is waiting for the
593
user to finish editing when spawning an editor, in case the editor
594
opens to a hidden window or somewhere obscure and the user gets
595
lost.
596
696
- Will merge to 'next'.
597
+ Still being bikeshed on, but hopefully the final is getting closer.
598
+ This is at its v4.
599
600
601
* tz/branch-doc-remove-set-upstream (2017-11-17) 1 commit
@@ -708,7 +610,9 @@ of the repositories listed at
610
Will merge to 'master'.
611
612
711
-* en/rename-progress (2017-11-15) 4 commits
613
+* en/rename-progress (2017-12-02) 5 commits
614
+ (merged to 'next' on 2017-12-04 at 49b39d2297)
615
+ + diffcore-rename: make diff-tree -l0 mean -l<large>
616
(merged to 'next' on 2017-11-20 at 77a2e0ddd9)
617
+ sequencer: show rename progress during cherry picks
618
+ diff: remove silent clamp of renameLimit
@@ -719,18 +623,17 @@ of the repositories listed at
623
hardcoded limit of 32k paths; this is being lifted to allow users
624
trade cycles with a (possibly) easier to read result.
625
722
- Will cook in 'next'.
626
+ Will merge to 'master'.
627
628
725
-* ar/unconfuse-three-dots (2017-11-26) 8 commits
629
+* ar/unconfuse-three-dots (2017-12-04) 7 commits
630
- t4013: test new output from diff --abbrev --raw
631
+ - diff: diff_aligned_abbrev: remove ellipsis after abbreviated SHA-1 value
632
- t4013: prepare for upcoming "diff --raw --abbrev" output format change
728
- - Testing: provide existing tests requiring them with ellipses after SHA-1 values
729
- - Documentation: git: document GIT_PRINT_SHA1_ELLIPSIS
730
- - Documentation: revisions: fix typo: "three dot" ---> "three-dot" (in line with "two-dot").
731
- - Documentation: user-manual: limit usage of ellipsis
633
- checkout: describe_detached_head: remove ellipsis after committish
733
- - diff: diff_aligned_abbrev: remove ellipsis after abbreviated SHA-1 value
634
+ - print_sha1_ellipsis: introduce helper
635
+ - Documentation: user-manual: limit usage of ellipsis
636
+ - Documentation: revisions: fix typo: "three dot" ---> "three-dot" (in line with "two-dot").
637
638
Ancient part of codebase still shows dots after an abbreviated
639
object name just to show that it is not a full object name, but
@@ -738,6 +641,9 @@ of the repositories listed at
641
who are used to seeing abbreviated object names and find them
642
confusing with the range syntax.
643
644
+ Almost there.
645
+ cf. <xmqqshcqmoe7.fsf@gitster.mtv.corp.google.com>
646
+
647
648
* jh/object-filtering (2017-11-22) 6 commits
649
(merged to 'next' on 2017-11-27 at e5008c3b28)
@@ -747,13 +653,13 @@ of the repositories listed at
653
+ oidset: add iterator methods to oidset
654
+ oidmap: add oidmap iterator methods
655
+ dir: allow exclusions from blob in addition to file
750
- (this branch is used by jh/fsck-promisors and jh/partial-clone.)
656
+ (this branch is used by cc/object-filtering-typofix, jh/fsck-promisors and jh/partial-clone.)
657
658
In preparation for implementing narrow/partial clone, the object
659
walking machinery has been taught a way to tell it to "filter" some
660
objects from enumeration.
661
756
- Will merge to 'master'.
662
+ Expecting incremental updates for a finishing touch.
663
664
665
* jh/fsck-promisors (2017-11-22) 10 commits
@@ -767,7 +673,7 @@ of the repositories listed at
673
- fsck: support refs pointing to promisor objects
674
- fsck: introduce partialclone extension
675
- extension.partialclone: introduce partial clone extension
770
- (this branch is used by jh/partial-clone; uses jh/object-filtering.)
676
+ (this branch is used by jh/partial-clone; uses jh/object-filtering; is tangled with cc/object-filtering-typofix.)
677
678
In preparation for implementing narrow/partial clone, the machinery
679
for checking object connectivity used by gc and fsck has been
@@ -791,7 +697,7 @@ of the repositories listed at
697
- fetch: refactor calculation of remote list
698
- clone, fetch-pack, index-pack, transport: partial clone
699
- upload-pack: add object filtering for partial clone
794
- (this branch uses jh/fsck-promisors and jh/object-filtering.)
700
+ (this branch uses jh/fsck-promisors and jh/object-filtering; is tangled with cc/object-filtering-typofix.)
701
702
The machinery to clone & fetch, which in turn involves packing and
703
unpacking objects, have been told how to omit certain objects using