Hi Philip, thx for responding. will update if we make any progress with your suggestion. Thank you
On Thursday, April 18, 2019 at 11:16:27 AM UTC-5, Philip Oakley wrote: > > Hi ZK W, > You should be able to set the config in the --global config file (as > oppose to the config file specific to the created repository). There are > three or four config file locations with a priority order, so go for the > level most suited. There may also be an environment variable (check the > bottom of the raw 'git' man page) > > Again check the manuals, I didn't look ;-) so I could be talking > nonsense for this specific case.. > > Philip > > On 18/04/2019 15:42, Zk W wrote: > > Hi Philip > > > > After issuing git svn clone, we could not issue git config gc.auto to > > change its setting at the same time in that local directory that git > > svn clone would clone to. > > If there's a way to do it, we don't know how. > > > > Q: > > Do we just open another terminal to issue > > git config gc.auto 0 > > while another terminal is doing its git svn clone ? > > > > Thank you. > > > > On Thu, Apr 18, 2019 at 9:35 AM Philip Oakley <philip...@iee.org > <javascript:> > > <mailto:philip...@iee.org <javascript:>>> wrote: > > > > Hi Zk W, > > > > That sounds like its a configurable item to tell _gc_ to stop that > > warning (change the limits, or change the 'when it looks' settings). > > > > I don't know enough about the gc auto settings but the manual should > > help for both gc and for config in spotting what to set. > > > > It doesn't sound like the actual svn clone is failing, just that > > it has > > a lot of 'rubbish' left behind while doing the clone. > > > > Philip > > > > On 18/04/2019 15:20, Zk W wrote: > > > Hi Philip > > > Thx for responding. > > > It failed during the git svn clone step. > > > It essentially crashed with message > > > > > > " > > > error: The last gc run reported the following. Please correct > > the root > > > cause and remove .git/gc.log > > > Automatic cleanup will not be performed until file is removed. > > > > > > warning: There are too many unreachable loose objects; run 'git > > prune' > > > to remove them. > > > > > > gc --auto: command returned error: 255 > > > " > > > > > > On Thursday, April 18, 2019 at 9:11:10 AM UTC-5, Philip Oakley > > wrote: > > > > > > Hi Zk W, > > > > > > While I know nothing of svn, could you at least clarify when > > the 'gc' > > > fails. > > > > > > I think I've seen threads where the 'gc' is performed at the > > end, > > > with > > > an implication that the transfer had happened but the > > problem was > > > afterwards. > > > > > > You may also want to search the main Git List archive > > > https://public-inbox.org/git/?q=svn > > > <https://public-inbox.org/git/?q=svn> > > > > > > Philip > > > > > > On 18/04/2019 14:21, Zk W wrote: > > > > Hi > > > > > > > > we have a big repo > > > > we tried git svn clone (non-standard layout) and it failed > due > > > to gc > > > > failure > > > > we tried > > > > git svn clone -r222:500000 repo-url -T <dir>/trunk > > > > --author-file=file.txt --no-minimal-url repoDir > > > > > > > > we then tried but we're unsure if below steps are correct to > > > overcome > > > > the gc failure. > > > > git svn clone -r222:5000 repo-url -T <dir>/trunk > > > > --author-file=file.txt --no-minimal-url repoDir > > > > cd repoDir > > > > git svn fetch -r500:50000 > > > > > > > > When it completed, we found many files missing. > > > > We checked > > > > git svn show-ignore > > > > > > > > It listed many directories > > > > > > > > Questions > > > > 1) Are the steps correct as workaround to overcome gc > > problem ? > > > > git svn clone -r222:5000 repo-url -T <dir>/trunk > > > > --author-file=file.txt --no-minimal-url repoDir > > > > cd repoDir > > > > git svn fetch -r500:50000 > > > > > > > > 2) How to do unignore the directories listed/shown in git > svn > > > > show-ignore ? > > > > We are afraid that missing files are not cloned because of > > > ignore by > > > > svn and git. > > > > > > > > Any help is appreciated > > > > -- > > > > You received this message because you are subscribed to > > the Google > > > > Groups "Git for human beings" group. > > > > To unsubscribe from this group and stop receiving emails > from > > > it, send > > > > an email to git-...@googlegroups.com > > <mailto:git-...@googlegroups.com> <javascript:> > > > > <mailto:git-...@googlegroups.com > > <mailto:git-...@googlegroups.com> <javascript:>>. > > > > For more options, visit https://groups.google.com/d/optout > > > <https://groups.google.com/d/optout>. > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Git for human beings" group. > > > To unsubscribe from this group and stop receiving emails from > > it, send > > > an email to git-...@googlegroups.com <javascript:> > > <mailto:git-users%2bunsubscr...@googlegroups.com <javascript:>> > > > <mailto:git-...@googlegroups.com <javascript:> > > <mailto:git-users%2bunsubscr...@googlegroups.com <javascript:>>>. > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to a topic in > > the Google Groups "Git for human beings" group. > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/git-users/XFuKwJ87yvM/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email > > to git-...@googlegroups.com <javascript:> > > <mailto:git-users%2bunsubscr...@googlegroups.com <javascript:>>. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Git for human beings" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to git-...@googlegroups.com <javascript:> > > <mailto:git-...@googlegroups.com <javascript:>>. > > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
