From: Arthur <a.foulon@amesys.fr>
To: git@vger.kernel.org
Subject: Re: git-p4 clone @all error
Date: Wed, 31 Oct 2012 06:18:20 -0700 (PDT) [thread overview]
Message-ID: <1351689500498-7570343.post@n2.nabble.com> (raw)
In-Reply-To: <1351593879401-7570219.post@n2.nabble.com>
up
--
View this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570343.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-10-31 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:44 git-p4 clone @all error Arthur
2012-10-31 13:18 ` Arthur [this message]
2012-10-31 14:01 ` Thomas Berg
2012-11-03 23:13 ` Pete Wyckoff
2012-11-05 10:02 ` Arthur
2012-11-05 22:12 ` Pete Wyckoff
2012-11-06 0:25 ` Vitor Antunes
2012-11-06 8:55 ` Arthur
2012-11-06 13:54 ` Vitor Antunes
2012-11-06 14:20 ` Arthur
2012-11-06 18:35 ` Vitor Antunes
2012-11-06 14:03 ` Arthur
2012-11-03 14:09 ` Pete Wyckoff
2012-11-03 23:07 ` [PATCH] git p4: catch p4 describe errors Pete Wyckoff
2012-11-03 23:12 ` Matt Arsenault
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=1351689500498-7570343.post@n2.nabble.com \
--to=a.foulon@amesys.fr \
--cc=git@vger.kernel.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).