On Mon, Jul 8, 2013 at 3:03 PM, Matthieu Brucher
wrote:
> Hi,
>
> I tried without spec, but then it tried importing everything, even
> though there was a .gitignore and a .git/config/exclude file.
> Then, it crashed during the importation because it could find an old
> branch (I don't have access
Hi,
I tried without spec, but then it tried importing everything, even
though there was a .gitignore and a .git/config/exclude file.
Then, it crashed during the importation because it could find an old
branch (I don't have access to everything on the repository), so I
tried importing just the rece
On Mon, Jul 8, 2013 at 12:10 PM, Matthieu Brucher
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
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 s
Unfortunately, git branch -a returns nothing :/
I tried with the simple detect-branches as well as with the config values.
Perhaps the spec-client? Although it is strange as it seems that the
repository is completely empty.
Thanks,
Matthieu
2013/7/8 Vitor Antunes :
> On Mon, Jul 8, 2013 at 11:09
On Mon, Jul 8, 2013 at 11:09 AM, Matthieu Brucher
wrote:
> Hi again,
>
> I tried with @all, but it didn'y work as expected. It imported a bunch
> of revisions (but no files?) and ended with:
> Reading pipe: ['git', 'config', '--bool', 'git-p4.importLabels']
> Not checking out any branch, use "
Hi again,
I tried with @all, but it didn'y work as expected. It imported a bunch
of revisions (but no files?) and ended with:
Reading pipe: ['git', 'config', '--bool', 'git-p4.importLabels']
Not checking out any branch, use "git checkout -q -b master "
executing git config --bool git-p4.usec
>> 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).
>
> Our P4 server has a limitation on the number of lines returned by "p4
> changes" command, so sometimes I have to use @change_start,@change_stop
On Fri, Jul 5, 2013 at 7:11 PM, Matthieu Brucher
wrote:
>> Hi Matthieu,
>>
>> Could you please try using //Depot/Projectall 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 on
> Hi Matthieu,
>
> Could you please try using //Depot/Projectall 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 t
Matthieu Brucher gmail.com> writes:
>
> Hi,
>
> I'm trying to convert a Perforce repository to git, knowing that:
> - I use client specs to remove a bunch of folders containing binaires
> (several GiB)
> - branch mappings may not be properly set, and I can't change them
>
> Now, the branches ar
Hi,
I'm trying to convert a Perforce repository to git, knowing that:
- I use client specs to remove a bunch of folders containing binaires
(several GiB)
- branch mappings may not be properly set, and I can't change them
Now, the branches are layout like this:
- Branch/Main <- master
- Branch/Fea
12 matches
Mail list logo
