From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Pete Wyckoff <pw@padd.com>, Vitor Antunes <vitor.hda@gmail.com>,
Luke Diamand <luke@diamand.org>
Subject: [PATCHv2 0/2] git p4 - import/export of git/p4 tags and labels
Date: Wed, 11 Apr 2012 17:21:22 +0200 [thread overview]
Message-ID: <1334157684-31402-1-git-send-email-luke@diamand.org> (raw)
This is an updated version of the previous patch for importing p4 labels
and exporting git tags.
Unlike the previous version, this one exports tags to p4 during 'submit'.
Because of the rebasing that goes on with git-p4, this is no worse
than doing it during the sync phase - to be exported a git tag has
to be on one of the commits that has come from p4.
I have also renamed the --export-tags option to --export-labels, as
it just seemed confusing (so now is export-labels, import-labels, etc).
This version is against Pete Wyckoff's patch series for making git-p4
a top-level program.
There is also a small fix to the t9800 test case to help it work
when P4EDITOR is defined.
Luke Diamand (2):
Fixing script editor checks
git p4: import/export of labels to/from p4
Documentation/git-p4.txt | 43 ++++++-
git-p4.py | 263 ++++++++++++++++++++++++++++++++++------
t/t9800-git-p4-basic.sh | 4 +-
t/t9811-git-p4-label-import.sh | 202 ++++++++++++++++++++++++++++++
4 files changed, 471 insertions(+), 41 deletions(-)
create mode 100755 t/t9811-git-p4-label-import.sh
--
1.7.10.rc0.161.gdb6eba
next reply other threads:[~2012-04-11 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 15:21 Luke Diamand [this message]
2012-04-11 15:21 ` [PATCHv2 1/2] git p4: Fixing script editor checks Luke Diamand
2012-04-11 17:14 ` Junio C Hamano
2012-04-11 18:51 ` Luke Diamand
2012-04-11 19:06 ` Junio C Hamano
2012-04-11 19:24 ` Luke Diamand
2012-04-11 15:21 ` [PATCHv2 2/2] git p4: import/export of labels to/from p4 Luke Diamand
2012-04-18 11:34 ` Pete Wyckoff
2012-04-21 17:59 ` 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=1334157684-31402-1-git-send-email-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=pw@padd.com \
--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 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).