All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitor Antunes <vitor.hda@gmail.com>
To: git@vger.kernel.org
Cc: Luke Diamand <luke@diamand.org>,
	Junio C Hamano <gitster@pobox.com>,
	Vitor Antunes <vitor.hda@gmail.com>
Subject: [PATCH V2 0/2] git-p4: improve client path detection with branches used
Date: Sun, 19 Apr 2015 11:56:47 +0100	[thread overview]
Message-ID: <1429441009-17775-1-git-send-email-vitor.hda@gmail.com> (raw)

Robustness improvement in regards to previous patches, both in the test case and
git-p4 functionality.

1. Test case now includes a mapped sub-file, to guarantee that git-p4 copes with
   such client view.

2. git-p4 now searches for paths starting with the branch's depot path and
   ending with "/..." to guarantee that the correct client side path is
   identified.

Vitor Antunes (2):
  t9801: check git-p4's branch detection and client view together
  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(-)

-- 
1.7.10.4

             reply	other threads:[~2015-04-19 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 10:56 Vitor Antunes [this message]
2015-04-19 10:56 ` [PATCH V2 1/2] t9801: check git-p4's branch detection and client view together Vitor Antunes
2015-04-20  5:43   ` Junio C Hamano
2015-04-20 22:25     ` Vitor Antunes
2015-04-20 22:45       ` Junio C Hamano
2015-04-21  7:10         ` Vitor Antunes
2015-04-19 10:56 ` [PATCH V2 2/2] git-p4: improve client path detection when branches are used Vitor Antunes

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=1429441009-17775-1-git-send-email-vitor.hda@gmail.com \
    --to=vitor.hda@gmail.com \
    --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 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.