From: Vitor Antunes <vitor.hda@gmail.com>
To: Matthieu Brucher <matthieu.brucher@gmail.com>,
Pete Wyckoff <pw@padd.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git p4 clone not processing branches properly
Date: Mon, 8 Jul 2013 14:43:40 +0100 [thread overview]
Message-ID: <CAOpHH-WxOhfYYOY8z5rc+O1B5QD8g22L9DFrNFEAtp9YwH+V_A@mail.gmail.com> (raw)
In-Reply-To: <CAHCaCkJ1rTj3xt4_rHEYTWzRbSDVnULwfkTggevn+qjLj_UC5A@mail.gmail.com>
On Mon, Jul 8, 2013 at 12:10 PM, Matthieu Brucher
<matthieu.brucher@gmail.com> wrote:
> Without the spec client, it seems that the branches are recognized,
> but there are some many binary files that I need to remove them during
> the migration.
> I tried setting a .gitignore beforehand, but it is not respected (I
> tried to remove some folders with folder/ in .gitignore, but the
> folder are still imported).
> It there a switch for the import somewhere?
Hi Matthieu,
Unfortunately I've never tested the branch detection together with spec
configuration. But there is a test case for it in the code that refers
to the following question in StackOverflow:
http://stackoverflow.com/questions/11893688
Could you also tell us which version of git you are using?
Pete, maybe you can help Matthieu further on this question?
Thanks,
Vitor
next prev parent reply other threads:[~2013-07-08 13:44 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
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 [this message]
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=CAOpHH-WxOhfYYOY8z5rc+O1B5QD8g22L9DFrNFEAtp9YwH+V_A@mail.gmail.com \
--to=vitor.hda@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthieu.brucher@gmail.com \
--cc=pw@padd.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).