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

Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Nov 1, 2017, 17:58 UTC
Message-ID
<20171101105833.dddaadec0640b7e01962f900@google.com>
In-Reply-To
<xmqqd152yesv.fsf@gitster.mtv.corp.google.com>

On Wed, 01 Nov 2017 10:21:20 +0900 Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines
> Jeff Hostetler <Jeff.Hostetler@microsoft.com> writes:
> 
> >> Yes, that, together with the expectation that I will hear from both you and JTan 
> >> once the result of combined effort becomes ready to replace this placeholder, 
> >> matches my assumption.
> >> 
> >> Is that happening now?
> >
> > Yes, I'm merging our them now and hope to have a version to
> > send to Jonathan and/or the list sometime this week.
> 
> Thanks.

Junio, would you prefer that the combined effort be in one single patch series or separated out into 3? The way I see it, there are two independent patch series - this one (object filter support in rev-list and pack-objects) and my one (repo extension for partial clone, fsck, and gc), and one patch series that depends on these two.

I prefer to have smaller patch series as a patch author (for example, less need to update later patches due to a design or API issue caught in review), as a reviewer (for example, less things to keep in mind as I review things patch by patch), and as an experimenter (assuming that smaller patch series go through the "next" -> "master" process faster, this means fewer locally-applied patches to juggle when testing out a new feature, as Jonathan Nieder said [1]).

I understand if you prefer each patch set to have at least one useful self-contained feature (or bug fix), though. (Having said that, I think that this patch set, at least - object filter support in rev-list and pack-objects - is useful enough on its own, but I understand if it doesn't reach the bar.)

[1] https://public-inbox.org/git/20171030222726.g26nryjxktyj27sd@aiede.mtv.corp.google.com/
Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 13 in “What's cooking in git.git (Oct 2017, #07; Mon, 30)”
  1. Junio C HamanoOct 30, 2017
  2. Ben PeartOct 30, 2017
  3. Johannes SchindelinOct 30, 2017
  4. Johannes SchindelinOct 30, 2017
  5. Junio C HamanoOct 31, 2017
  6. Johannes SchindelinOct 31, 2017
  7. Johannes SchindelinOct 30, 2017
  8. Jeff HostetlerOct 30, 2017
  9. Junio C HamanoOct 31, 2017
  10. Jeff HostetlerOct 31, 2017
  11. Junio C HamanoNov 1, 2017
  12. Jonathan TanNov 1, 2017
  13. Junio C HamanoNov 2, 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.