I got my git-p4 from here BTW.
http://repo.or.cz/w/fast-export.git
On 6/8/07, Benjamin Sergeant <bsergean@xxxxxxxxx> wrote:
On 6/8/07, Scott Lamb <slamb@xxxxxxxxx> wrote:
> 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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
