All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org, Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH v3 0/3] git-p4: Search for parent commit on branch creation
Date: Wed, 25 Jan 2012 23:21:49 -0500	[thread overview]
Message-ID: <20120126042149.GA24269@padd.com> (raw)
In-Reply-To: <1327535304-11332-1-git-send-email-vitor.hda@gmail.com>

vitor.hda@gmail.com wrote on Wed, 25 Jan 2012 23:48 +0000:
> I think this will, hopefully, be the final version of this series of
> patches. This version includes the following changes since v2:
> 
>  - Move search algorithm into its own function.
>  - Use lists instead of strings on shell commands.
>  - Some small (almost cosmetic) updates to test cases.

Whole series

Acked-by: Pete Wyckoff <pw@padd.com>

Thanks for making all the changes.

> Pete Wyckoff (1):
>   git-p4: Change p4 command invocation
> 
> Vitor Antunes (2):
>   git-p4: Search for parent commit on branch creation
>   git-p4: Add test case for complex branch import
> 
>  contrib/fast-import/git-p4 |   48 +++++++++++++++++++++-
>  t/t9801-git-p4-branch.sh   |   94 ++++++++++++++++++++++++++++++++++++++++---
>  2 files changed, 133 insertions(+), 9 deletions(-)
> 
> -- 
> 1.7.8.3
> 

      parent reply	other threads:[~2012-01-26  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 23:48 [PATCH v3 0/3] git-p4: Search for parent commit on branch creation Vitor Antunes
2012-01-25 23:48 ` [PATCH v3 1/3] " Vitor Antunes
2012-01-25 23:48 ` [PATCH v3 2/3] git-p4: Add test case for complex branch import Vitor Antunes
2012-01-25 23:48 ` [PATCH v3 3/3] git-p4: Change p4 command invocation Vitor Antunes
2012-01-26  4:21 ` Pete Wyckoff [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=20120126042149.GA24269@padd.com \
    --to=pw@padd.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.