Re: [PATCH] submodule update: run custom update script for initial populating as well

2017-01-13 Thread Stefan Beller
On Fri, Jan 13, 2017 at 3:58 PM, Junio C Hamano wrote: > Stefan Beller writes: > >> + if test "$update_module" = "merge" || >> +test "$update_module" = "rebase" || >> +test "$update_module" = "none" >> + then

Re: [PATCH] submodule update: run custom update script for initial populating as well

2017-01-13 Thread Junio C Hamano
Stefan Beller writes: > + if test "$update_module" = "merge" || > +test "$update_module" = "rebase" || > +test "$update_module" = "none" > + then > + update_module=checkout > +

Re: [PATCH] submodule update: run custom update script for initial populating as well

2017-01-13 Thread Stefan Beller
On Fri, Jan 13, 2017 at 3:42 PM, Junio C Hamano wrote: > Stefan Beller writes: > >> In 1b4735d9f3 (submodule: no [--merge|--rebase] when newly cloned, >> 2011-02-17), all actions were defaulted to checkout for populating >> a submodule initially, because merging or rebasing makes no sense >> in t

Re: [PATCH] submodule update: run custom update script for initial populating as well

2017-01-13 Thread Junio C Hamano
Stefan Beller writes: > In 1b4735d9f3 (submodule: no [--merge|--rebase] when newly cloned, > 2011-02-17), all actions were defaulted to checkout for populating > a submodule initially, because merging or rebasing makes no sense > in that situation. > > Other commands however do make sense, such a

[PATCH] submodule update: run custom update script for initial populating as well

2017-01-13 Thread Stefan Beller
In 1b4735d9f3 (submodule: no [--merge|--rebase] when newly cloned, 2011-02-17), all actions were defaulted to checkout for populating a submodule initially, because merging or rebasing makes no sense in that situation. Other commands however do make sense, such as the custom command that was added