Hi, sorry for the late reply.
On Fri, Dec 07, 2012 at 09:21:33AM -0800, Junio C Hamano wrote: > Steffen Jaeckel <steffen.jaec...@stzedn.de> writes: > > > Signed-off-by: Steffen Jaeckel <steffen.jaec...@stzedn.de> > > --- > > contrib/completion/git-completion.bash | 9 +++++++++ > > 1 file changed, 9 insertions(+) > > > > diff --git a/contrib/completion/git-completion.bash > > b/contrib/completion/git-completion.bash > > index 0b77eb1..5b4d2e1 100644 > > --- a/contrib/completion/git-completion.bash > > +++ b/contrib/completion/git-completion.bash > > @@ -1434,6 +1434,10 @@ _git_pull () > > __git_complete_remote_or_refspec > > } > > > > +__git_push_recurse_submodules_options=" > > + check on-demand > > +" > > Most of the existing completion functions do not seem to define > separate variables like this; instead, they literally embed their > choices at the point of use. > > Is it expected that the same set of choices will appear in the > completion of many other subcommand options? [jc: Cc'ed Heiko so > that we can sanity check the answer to this question]. If so, the > variable may be justified; otherwise, not. No I think not. At least not exactly the same. check will be limited to push since it only makes sense there. on-demand on the other hand is already used for fetch and pull. Currently no more possible uses come to my mind. checkout and others will learn to traverse submodules but that will most likely be a boolean (to switch it on and off). CC'ed Jens so he can also take a look. Cheers Heiko -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
