git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4 00/15] Parial clone part 3: clone, fetch, fetch-pack, upload-pack, and tests

From
JHJeff Hostetler <git@jeffhostetler.com>
Date
Nov 21, 2017, 20:46 UTC
Message-ID
<fe9a3ff3-00aa-555e-1865-82749121de0d@jeffhostetler.com>
In-Reply-To
<20171121101702.663a52515070faf73a97f2b8@google.com>
On 11/21/2017 1:17 PM, Jonathan Tan wrote:
Show 29 quoted lines
> On Thu, 16 Nov 2017 18:17:08 +0000
> Jeff Hostetler <git@jeffhostetler.com> wrote:
> 
>> From: Jeff Hostetler <jeffhost@microsoft.com>
>>
>> This part 3 of a 3 part sequence partial clone.  It assumes
>> that part 1 and part 2 are in place.
>>
>> This patch series is labeled as V4 to keep it in sync with
>> the corresponding V4 versions of parts 1 and 2.  There was
>> not a V3 version of this patch series.
>>
>> Jonathan and I independently started on this task.  This is another
>> pass at merging those efforts.  So there are several places that may
>> need refactoring and cleanup, but fewer than in the previous submission.
>> In particular, the test cases should be squashed and new tests added.
>>
>> And I think we need more end-to-end tests.  I'll work on those next.
> 
> I think that it would be easier to review if the test for each command
> was contained in the same patch as (or the patch immediately following)
> the implementation of the command - for example, as in my modifications
> [1].
> 
> (If you're about to send out v5, that's fine - maybe take this in
> consideration for v6, if there is one.)
> 
> [1] https://github.com/jonathantanmy/git/commits/pc20171103
> 

I've already pulled the tests to be with the code changes in part 1 and part 2. There are a few commits with tests in part 3 that we may want to squash together, but we can do that later. If you want to start with my V5 set and do that, that would be fine.

What I was talking about above are some additional end-to-end tests that I think we need. For example, do a partial clone/fetch and then run blame or some other commands that exercise the overall system.

As parts 1, 2, and 3 are settling down, these additional tests could be in a part 4 for now. Later, if it makes sense, these could be move earlier.

Jeff
Previous: Jonathan Tan
Message 19 of 19 in “Parial clone part 3: clone, fetch, fetch-pack, upload-pack, and tests”
  1. 00/15 Parial clone part 3: clone, fetch, fetch-pack, upload-pack, and testsJeff Hostetler, Nov 16, 2017
  2. 01/15 upload-pack: add object filtering for partial cloneJeff Hostetler, Nov 16, 2017
  3. 02/15 clone, fetch-pack, index-pack, transport: partial cloneJeff Hostetler, Nov 16, 2017
  4. 05/15 remote-curl: add object filtering for partial cloneJeff Hostetler, Nov 16, 2017
  5. 04/15 fetch: add object filtering for partial fetchJeff Hostetler, Nov 16, 2017
  6. 07/15 fetch-pack: test support excluding large blobsJeff Hostetler, Nov 16, 2017
  7. 03/15 fetch: refactor calculation of remote listJeff Hostetler, Nov 16, 2017
  8. 08/15 partial-clone: define partial clone settings in configJeff Hostetler, Nov 16, 2017
  9. 11/15 t5500: add fetch-pack tests for partial cloneJeff Hostetler, Nov 16, 2017
  10. 10/15 fetch: add from_promisor and exclude-promisor-objects parametersJeff Hostetler, Nov 16, 2017
  11. 14/15 unpack-trees: batch fetching of missing blobsJeff Hostetler, Nov 16, 2017
  12. 13/15 t5500: more tests for partial clone and fetchJeff Hostetler, Nov 16, 2017
  13. 12/15 t5601: test for partial cloneJeff Hostetler, Nov 16, 2017
  14. 15/15 fetch-pack: restore save_commit_buffer after useJeff Hostetler, Nov 16, 2017
  15. 06/15 pack-objects: test support for blob filteringJeff Hostetler, Nov 16, 2017
  16. 09/15 fetch-pack: test support excluding large blobsJeff Hostetler, Nov 16, 2017
  17. Junio C HamanoNov 17, 2017
  18. Jonathan TanNov 21, 2017
  19. Jeff HostetlerNov 21, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.