From: Matthieu Brucher <matthieu.brucher@gmail.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git p4 clone not processing branches properly
Date: Fri, 5 Jul 2013 19:11:55 +0100 [thread overview]
Message-ID: <CAHCaCkLpobqTOUMeK2TP_=VkjRo4P3-dMwt85_CaasSuRNE1Kg@mail.gmail.com> (raw)
In-Reply-To: <loom.20130705T195116-413@post.gmane.org>
> Hi Matthieu,
>
> Could you please try using //Depot/Project<at>all instead of selecting a
> specific revision?
I can try. Indeed, at this revision, the two other branches do not yet
exist. But @all will get everything? Last time, I only got head
(IIRC).
> Also, by using that command it means that the following depot paths must
> exist:
> //Depot/Project/Branch/Main
> //Depot/Project/Releases/2013
> //Depot/Project/Branch/Feature1
Yes, they indeed do.
> I've never used the --use-client-spec, so I'm not sure if that will not
> break the branch detection code.
I need to do that because if I don't, the depot is clobbed with
binaries. Or perhaps if I put some .gitignore stuff, I might not do
this?
> Cheers,
> Vitor
Thanks for the tips, I will try tomorrow.
Cheers,
--
Information System Engineer, Ph.D.
Blog: http://matt.eifelle.com
LinkedIn: http://www.linkedin.com/in/matthieubrucher
Music band: http://liliejay.com/
next prev parent reply other threads:[~2013-07-05 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHCaCkJ+zRwu67QsYidmvcwtWtPPd4XPBYDaTnHLt9HrTSDM3A@mail.gmail.com>
2013-07-05 13:16 ` git p4 clone not processing branches properly Matthieu Brucher
2013-07-05 17:56 ` Vitor Antunes
2013-07-05 18:11 ` Matthieu Brucher [this message]
2013-07-05 18:36 ` Vitor Antunes
2013-07-05 18:45 ` Matthieu Brucher
2013-07-08 10:09 ` Matthieu Brucher
2013-07-08 10:24 ` Vitor Antunes
2013-07-08 10:51 ` Matthieu Brucher
2013-07-08 11:10 ` Matthieu Brucher
2013-07-08 13:43 ` Vitor Antunes
2013-07-08 14:03 ` Matthieu Brucher
2013-07-13 0:28 ` Vitor Antunes
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHCaCkLpobqTOUMeK2TP_=VkjRo4P3-dMwt85_CaasSuRNE1Kg@mail.gmail.com' \
--to=matthieu.brucher@gmail.com \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).