From: Pete Wyckoff <pw@padd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tor Arvid Lund <torarvid@gmail.com>,
Anatol Pomozov <anatol.pomozov@gmail.com>,
git@vger.kernel.org
Subject: [PATCH 0/2] git-p4: fix clone @all regression
Date: Sat, 12 Mar 2011 11:22:46 -0500 [thread overview]
Message-ID: <20110312162246.GA8509@arf.padd.com> (raw)
My commit e32e00dc88948a730b8b1f3b8129f30c313713e7
"git-p4: better message for "git-p4 sync" when not cloned"
broke clone @all. This fixes it per Tor Arvid's patch
and adds a test to make sure it doesn't happen again.
git-p4: fix clone @all regression
git-p4: test clone @all
contrib/fast-import/git-p4 | 2 +-
t/t9800-git-p4.sh | 16 ++++++++++++++++
2 files changed, 17 insertions(+), 1 deletions(-)
Please queue to maint. Thanks,
-- Pete
next reply other threads:[~2011-03-12 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 16:22 Pete Wyckoff [this message]
2011-03-12 16:23 ` [PATCH 1/2] git-p4: fix clone @all regression Pete Wyckoff
2011-03-12 16:24 ` [PATCH 2/2] git-p4: test clone @all Pete Wyckoff
2011-03-13 19:54 ` [PATCH 0/2] git-p4: fix clone @all regression 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=20110312162246.GA8509@arf.padd.com \
--to=pw@padd.com \
--cc=anatol.pomozov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torarvid@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).