From: Jonathan Tan <jonathantanmy@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff Hostetler <Jeff.Hostetler@microsoft.com>,
Jeff Hostetler <git@jeffhostetler.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)
Date: Wed, 1 Nov 2017 10:58:33 -0700 [thread overview]
Message-ID: <20171101105833.dddaadec0640b7e01962f900@google.com> (raw)
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:
> 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/
next prev parent reply other threads:[~2017-11-01 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 6:19 What's cooking in git.git (Oct 2017, #07; Mon, 30) Junio C Hamano
2017-10-30 12:40 ` Ben Peart
2017-10-30 17:24 ` Johannes Schindelin
2017-10-30 17:28 ` Johannes Schindelin
2017-10-31 2:38 ` Junio C Hamano
2017-10-31 17:18 ` Johannes Schindelin
2017-10-30 17:31 ` Johannes Schindelin
2017-10-30 19:54 ` Jeff Hostetler
2017-10-31 2:40 ` Junio C Hamano
2017-10-31 13:14 ` Jeff Hostetler
2017-11-01 1:21 ` Junio C Hamano
2017-11-01 17:58 ` Jonathan Tan [this message]
2017-11-02 1:13 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171101105833.dddaadec0640b7e01962f900@google.com \
--to=jonathantanmy@google.com \
--cc=Jeff.Hostetler@microsoft.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).