From: Vitor Antunes <vitor.hda@gmail.com>
To: git@vger.kernel.org
Cc: Pete Wyckoff <pw@padd.com>, Luke Diamand <luke@diamand.org>,
Vitor Antunes <vitor.hda@gmail.com>
Subject: [PATCH v2 0/3] git-p4: Search for parent commit on branch creation
Date: Sat, 21 Jan 2012 00:21:29 +0000 [thread overview]
Message-ID: <1327105292-30092-1-git-send-email-vitor.hda@gmail.com> (raw)
The new version of these patches includes the improvement suggestions
from Pete Wyckoff:
- Use os.path.join().
- Use git update-ref -d to remove refs.
- Read $GIT_DIR environment variable.
- Optimize comparison cycle to avoid excessive use of checkpoint
command.
Vitor Antunes (3):
git-p4: Add checkpoint() task
git-p4: Search for parent commit on branch creation
git-p4: Add test case for complex branch import
contrib/fast-import/git-p4 | 38 ++++++++++++++++++++-
t/t9801-git-p4-branch.sh | 80 ++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 117 insertions(+), 1 deletions(-)
--
1.7.7.rc2.14.g5e044.dirty
next reply other threads:[~2012-01-21 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 0:21 Vitor Antunes [this message]
2012-01-21 0:21 ` [PATCH v2 1/3] git-p4: Add checkpoint() task Vitor Antunes
2012-01-21 0:21 ` [PATCH v2 2/3] git-p4: Search for parent commit on branch creation Vitor Antunes
2012-01-21 4:55 ` Junio C Hamano
2012-01-23 13:49 ` Vitor Antunes
2012-01-21 0:21 ` [PATCH v2 3/3] git-p4: Add test case for complex branch import Vitor Antunes
2012-01-21 4:54 ` Junio C Hamano
2012-01-21 10:51 ` Luke Diamand
2012-01-21 17:11 ` Pete Wyckoff
2012-01-23 14:01 ` Vitor Antunes
2012-01-23 22:40 ` Pete Wyckoff
2012-01-25 1:23 ` Vitor Antunes
2012-01-25 12:34 ` Pete Wyckoff
[not found] ` <CAOpHH-Wcf3innjA4LS0TMrLzEwbQzfZmHssxSBYvv4v7UMfi1w@mail.gmail.com>
2012-01-25 1:39 ` Vitor Antunes
2012-01-25 4:02 ` Junio C Hamano
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=1327105292-30092-1-git-send-email-vitor.hda@gmail.com \
--to=vitor.hda@gmail.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--cc=pw@padd.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 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).