git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2 0/2] Work on t3404 in preparation for rebase--helper
Date: Mon, 16 May 2016 08:33:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1605160830340.3303@virtualbox> (raw)
In-Reply-To: <xmqqa8jtaliw.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Fri, 13 May 2016, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Thu, 12 May 2016, Junio C Hamano wrote:
> >
> >> I took these separately already, and plan to fast-track them as they
> >> are both "trivially correct"; I double checked that what I have match
> >> these two, too.
> >
> > Oh, okay. I just wanted to make things easier for you, and now that I
> > have a script to prepare patch series, it's really almost as trivial
> > for me to send out a new iteration as it would be to update a Pull
> > Request on GitHub.
> >
> > Do you want me to hold off with new iterations in the future until you
> > clarified your preferred course of action?
> 
> No.  You've been doing great.  I just wanted to clarify what I did
> to your patch before I merge them separately to 'next' ahead of the
> remainder that you'd be sending out, expecting a possible course
> correction, e.g. "that would make it harder to queue the other patches
> yet to come, all of which would depend on both of them--it would be
> better to queue them on a single topic to be extended with these
> other patches, after all these two are not that urgent".

Thanks.

I planned to work on the remainder as a "topic thicket" using my Git
garden shears [*1*] anyway, picking up the changes you picked up,
replacing my original patches.

Ciao,
Dscho

Footnote *1*: The garden shears are kind of a `git rebase -i -p` as I wish
I had designed it originally. Thet live here:
https://github.com/git-for-windows/build-extra/blob/master/shears.sh

      reply	other threads:[~2016-05-16  6:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 13:59 [PATCH 0/2] Work on t3404 in preparation for rebase--helper Johannes Schindelin
2016-05-10 14:05 ` [PATCH 1/2] t3404: fix typo Johannes Schindelin
2016-05-10 14:07 ` [PATCH 2/2] t3404: be resilient against running with the -x flag Johannes Schindelin
2016-05-10 19:49   ` Junio C Hamano
2016-05-10 20:58     ` Jeff King
2016-05-10 21:13       ` Junio C Hamano
2016-05-10 21:32         ` [PATCH] test-lib: set BASH_XTRACEFD automatically Jeff King
2016-05-10 22:06           ` Junio C Hamano
2016-05-11 13:44             ` [PATCH v2] " Jeff King
2016-05-12 15:39               ` Johannes Schindelin
2016-05-12 15:43 ` [PATCH v2 0/2] Work on t3404 in preparation for rebase--helper Johannes Schindelin
2016-05-12 15:44   ` [PATCH v2 1/2] t3404: fix typo Johannes Schindelin
2016-05-12 15:44   ` [PATCH v2 2/2] test-lib: set BASH_XTRACEFD automatically Johannes Schindelin
2016-05-12 16:21   ` [PATCH v2 0/2] Work on t3404 in preparation for rebase--helper Junio C Hamano
2016-05-13  6:37     ` Johannes Schindelin
2016-05-13 17:57       ` Junio C Hamano
2016-05-16  6:33         ` Johannes Schindelin [this message]

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=alpine.DEB.2.20.1605160830340.3303@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).