From: Lex Spoon <lex@lexspoon.org>
To: Luke Diamand <luke@diamand.org>
Cc: Git Users <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv3 0/4] git-p4: fixing --changes-block-size handling
Date: Fri, 12 Jun 2015 15:03:14 -0400 [thread overview]
Message-ID: <CALM2SnYaNUqaYAs+FKZ2NBG1b3sEwoTwoRueFS=yR6naixwPZg@mail.gmail.com> (raw)
In-Reply-To: <1433921459-16555-1-git-send-email-luke@diamand.org>
The latest patch series LGTM. It's a pity about the more complicated
structure with two different ways to query the changes list, but it
does look hard to make it any simpler.
Lex Spoon
prev parent reply other threads:[~2015-06-12 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 7:30 [PATCHv3 0/4] git-p4: fixing --changes-block-size handling Luke Diamand
2015-06-10 7:30 ` [PATCHv3 1/4] git-p4: additional testing of --changes-block-size Luke Diamand
2015-06-10 7:30 ` [PATCHv3 2/4] git-p4: test with limited p4 server results Luke Diamand
2015-06-10 7:30 ` [PATCHv3 3/4] git-p4: add tests for non-numeric revision range Luke Diamand
2015-06-10 7:30 ` [PATCHv3 4/4] git-p4: fixing --changes-block-size handling Luke Diamand
2015-06-12 19:03 ` Lex Spoon [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALM2SnYaNUqaYAs+FKZ2NBG1b3sEwoTwoRueFS=yR6naixwPZg@mail.gmail.com' \
--to=lex@lexspoon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
/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.
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 NNTP newsgroup(s).