All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org, Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH V3 0/2] git-p4: improve client path detection when branches are used
Date: Wed, 22 Apr 2015 10:11:43 -0700	[thread overview]
Message-ID: <xmqqegncf5ps.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1429656570-21825-1-git-send-email-vitor.hda@gmail.com> (Vitor Antunes's message of "Tue, 21 Apr 2015 23:49:28 +0100")

Vitor Antunes <vitor.hda@gmail.com> writes:

> The updates introduced in the third revision of these two patches consist only
> on updates to the commit messages to better clarify what they implement.
>
> Vitor Antunes (2):
>   t9801: check git-p4's branch detection with client spec enabled
>   git-p4: improve client path detection when branches are used
>
>  git-p4.py                |   13 ++++--
>  t/t9801-git-p4-branch.sh |  106 ++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 115 insertions(+), 4 deletions(-)

Thanks; will re-queue.  Luke, could you comment?

  parent reply	other threads:[~2015-04-22 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 22:49 [PATCH V3 0/2] git-p4: improve client path detection when branches are used Vitor Antunes
2015-04-21 22:49 ` [PATCH V3 1/2] t9801: check git-p4's branch detection with client spec enabled Vitor Antunes
2015-04-21 22:49 ` [PATCH V3 2/2] git-p4: improve client path detection when branches are used Vitor Antunes
2015-04-22 17:11 ` Junio C Hamano [this message]
2015-04-22 20:47   ` [PATCH V3 0/2] " Luke Diamand
2015-04-23  8:37     ` Vitor Antunes
2015-04-23 10:03       ` Luke Diamand

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=xmqqegncf5ps.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=luke@diamand.org \
    --cc=vitor.hda@gmail.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.