Re: rev-parse --show-toplevel broken during exec'ed rebase?

On Thu, Jul 12, 2018 at 8:23 AM Junio C Hamano wrote: > > Vitali Lovich writes: > > > Repro (starting with cwd within git project): > >> (cd xdiff; git rev-parse --show-toplevel) > > ... path to git repository > >> git rebase -i 18404434bf406f6a6f892ed7332

Re: rev-parse --show-toplevel broken during exec'ed rebase?

Sorry. Forgot to include the git versions I tested with (2.13.1, 2.17.0, 2.18.0) On Wed, Jul 11, 2018 at 7:50 PM Vitali Lovich wrote: > > Typically git rev-parse --show-toplevel prints the folder containing > the .git folder regardless what subdirectory one is in. One exception >

rev-parse --show-toplevel broken during exec'ed rebase?

Typically git rev-parse --show-toplevel prints the folder containing the .git folder regardless what subdirectory one is in. One exception I have found is that if one is within the context of git rebase --exec then show-toplevel always just prints the current directory it's running from. Repro

Re: --progress option for git submodule update?

& then do a git submodule init? > On Sep 11, 2015, at 4:05 PM, Stefan Beller <sbel...@google.com> wrote: > > On Wed, Sep 9, 2015 at 8:06 PM, Vitali Lovich <vlov...@gmail.com> wrote: >>> Doh! I see what you're missing now after rereading the email closely

--progress option for git submodule update?

Hi, Git submodule doesn’t have a --progress option like regular clone/fetch does. This means that it can hang a long time without output as it’s transferring data, particularly for large repositories. This is problematic in automation scenarios where there can be upper-bounds on how long a

Re: --progress option for git submodule update?

ing for git fetch --recurse-submodules and for > git submodule update eventually. I sent some early working patches for that, > but I am doing a whole new redesign without threads now). That sounds exciting. Can’t wait. > On Wed, Sep 9, 2015 at 3:52 PM, Vitali Lovich <vlov...@gmail.