Re: git-p4 fails when cloning a p4 depo.

From: Benjamin Sergeant <bsergean@gmail.com>
Date: Jun 8, 2007, 22:04 UTC
Message-ID: <1621f9fa0706081504l6106c639oe57c9fd74ebd097a@mail.gmail.com>
In-Reply-To: <4669CB75.7060009@slamb.org>

On 6/8/07, Scott Lamb <slamb@slamb.org> wrote:

Show 6 quoted lines

> Scott Lamb wrote:
> > No need to hardcode - from Python this is
> > os.sysconf(os.sysconf_names['SC_ARG_MAX'])
>
> In fact, just os.sysconf('SC_ARG_MAX') will do.
>

magic number are lot of fun, why would you want to use the clean method :)

So are you saying that in the old days, git-p4 was importing the p4 depo in small slices to not overkill the process memory (in case the depo is big) ?

BTW, there is the whole universe in my depot, so using -//Work/Users in my client specification I usually manage to have less megs of code on my disk after a sync. This way the git-p4 clone would not use too much memory. But we would have to change the way git-p4 works, it should be able to read a full client view instead of just a single perforce path.

Would you give me the git command to fetch the up git clone <git-url> --date <the good date> ?

Thanks, Benjamin.