From: Simon Hausmann <simon@lst.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: git-p4 pull request
Date: Wed, 18 Jul 2007 17:42:07 +0200 [thread overview]
Message-ID: <200707181742.12046.simon@lst.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
The following changes since commit a5e407988b35b7353bd03c770afc647670c25981:
Jim Meyering (1):
git-cvsserver: detect/diagnose write failure, etc.
are available in the git repository at:
git://people.freedesktop.org/~hausmann/git-p4 master
Scott Lamb (2):
git-p4: use subprocess in p4CmdList
git-p4: input to "p4 files" by stdin instead of arguments
Simon Hausmann (3):
git-p4: Cleanup, make listExistingP4Branches a global function for later use.
git-p4: Fix upstream branch detection for submit/rebase with multiple branches.
git-p4: Cleanup, used common function for listing imported p4 branches
contrib/fast-import/git-p4 | 129 ++++++++++++++++++++++++--------------------
1 files changed, 70 insertions(+), 59 deletions(-)
I have used Scotts changes for two days now and had no problems at all.
Based on Alex Riesen's suggestion they are a nice solution around the commandline
limits when calling the p4 client.
The other three changes fix a rather ugly bug when importing multiple depot
paths through p4 branch mappings where it could happen in the end that changes
that were done in git were submitted into the wrong depot paths in perforce itself
due to a faulty rebase onto the wrong git branch.
Would be great if those changes could be included in master.
Thanks,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-07-18 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 15:42 Simon Hausmann [this message]
2007-07-19 0:25 ` git-p4 pull request Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-10-20 15:17 Simon Hausmann
2007-11-08 11:55 Simon Hausmann
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=200707181742.12046.simon@lst.de \
--to=simon@lst.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).