From: Imran M Yousuf <imyousuf@gmail.com>
Date: Mon, 19 May 2008 03:48:43 GMT
Subject: Re: [PATCH v2 3/5] git-submodule.sh: Add Custom argument input support to git submodule recurse subcommand
Message-ID: <7bfdc29a0805182048i1d7a06saf0fda0e0582fcae@mail.gmail.com>
In-Reply-To: <7v7idzxhwp.fsf@gitster.siamese.dyndns.org>

On Tue, May 13, 2008 at 4:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> For example, one module could want to checkout 'master', while another might want
>> to checkout 'work'. The [-a|--customized-argument] argument provides platform
>> just for that. Consider the following command and its followup for further info:
>>......
>.......
> If we want a useful and flexible "recurse", perhaps the only thing we need
> to do is a command that lists a submodule directory path, one path at a
> time, in optionally different traversal order and depth cutoff, so that
> the user can feed it to xargs and do whatever they want to run in there.
>
I am not sure whether I understand it correctly or not, we could
simply provide the shell window by invoking 'sh', right? If we do that
then is there need to use xargs? I am not particularly experienced
with xargs, I was thinking of something as follows:

#!/bin/sh
echo "Submodule a"
(
PS1="module/submodule$" sh
)
echo "" #In case of ctrl+D to ensure that there is a blank line
echo "Submodule a ends"

I do agree that it would be powerful enough to serve all the necessary
purpose for traversing git submodules. If my assumption is right in
what we want then I will resubmit the patch with required changes.

-- 
Imran M Yousuf