Re: [RFC/PATCHv2] submodule: add ability to configure update command

2013-07-02 Thread Chris Packham
On 02/07/13 04:48, Junio C Hamano wrote: > Chris Packham writes: > >> +!*) >> +command="$(expr "$update_module" : '!\(.*\)')" > > command=${command#!} > Thanks, expr was my attempt to avoid using a ${command:1} bash-ism. v3 on it's way. --

Re: [RFC/PATCHv2] submodule: add ability to configure update command

2013-07-01 Thread Junio C Hamano
Chris Packham writes: > + !*) > + command="$(expr "$update_module" : '!\(.*\)')" command=${command#!} -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo in

Re: [RFC/PATCHv2] submodule: add ability to configure update command

2013-07-01 Thread Junio C Hamano
Chris Packham writes: > Subject: Re: [RFC/PATCHv2] submodule: add ability to configure update command "ability to configure" wants to be rephrased to make it more useful in the shortlog output to help me update release notes ;-) Subject: [PATCH] submodule update: allow

[RFC/PATCHv2] submodule: add ability to configure update command

2013-07-01 Thread Chris Packham
Users can set submodule.$name.update to '!command' which will cause 'command' to be run instead of checkout/merge/rebase. This allows the user some finer grained control over how the update is done. The primary motivation for this was interoperability with stgit however being able to intercept the