From: Pete Wyckoff <pw@padd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Horowitz <michael.horowitz@ieee.org>, git@vger.kernel.org
Subject: [PATCH 0/2] git-p4: sync new branch regression
Date: Wed, 16 Mar 2011 16:50:08 -0400 [thread overview]
Message-ID: <20110316205008.GA22702@arf.padd.com> (raw)
Here is another fix for e32e00d (git-p4: better message for
"git-p4 sync" when not cloned, 2011-02-19). Mike pointed out
that his use case breaks too.
These two patches fix it, and add two new test cases to
check for future breakage. At least we're coming up with
a good set of tests.
git-p4: fix sync new branch regression
git-p4: test sync new branch
contrib/fast-import/git-p4 | 4 +++-
t/t9800-git-p4.sh | 23 +++++++++++++++++++++++
2 files changed, 26 insertions(+), 1 deletions(-)
These would be good on master, beyond e32e00d that is
in your pw/p4. Thanks,
-- Pete
next reply other threads:[~2011-03-16 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 20:50 Pete Wyckoff [this message]
2011-03-16 20:52 ` [PATCH 1/2] git-p4: fix sync new branch regression Pete Wyckoff
2011-03-16 20:53 ` [PATCH 2/2] git-p4: test sync new branch Pete Wyckoff
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=20110316205008.GA22702@arf.padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=michael.horowitz@ieee.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 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).