RFC: Folder Git

>
> Issues:
> * Don't know if anyone else has used it. Probably not, so there's
> bound to be issues (especially since it's been changed quite a bit the
> last couple days for this RFC).
>

> On Mon, Apr 25, 2011 at 6:32 PM, Victor Engmark
> <victor.engmark@gmail.com> wrote:
> continue to other repositories.
>>
>> Issues:
>> * Don't know if anyone else has used it. Probably not, so there's
>> bound to be issues (especially since it's been changed quite a bit the
>> last couple days for this RFC).
>>
>
> Victor,
>
> Certainly seems like a common need. I had a similar solution which I
> used for a while.
>
> In the end, however, I found that creating a super-module in the top
> directory that contains
> the other git directories as git submodules allowed me to use a
> standard feature of git to achieve the same effect.
>
> So:
>
>    git submodule foreach git gc --aggressive
>
> I know this won't suit every use case, but it does work in an
> environment where the set of repos you are operating on have a degree
> of coherence and it makes sense to set up a submodule for them.  In
> this particular case this is the only reason why I use submodules - I
> don't use them for configuration management, for example, simply as a
> handy way to exploit git submodule foreach.
>
> Have you considered using git submodules in this way?

> On Mon, Apr 25, 2011 at 10:52 AM, Jon Seymour <jon.seymour@gmail.com> wrote:
>> On Mon, Apr 25, 2011 at 6:32 PM, Victor Engmark
>> <victor.engmark@gmail.com> wrote:
>> continue to other repositories.
>>>
>>> Issues:
>>> * Don't know if anyone else has used it. Probably not, so there's
>>> bound to be issues (especially since it's been changed quite a bit the
>>> last couple days for this RFC).
>>>
>>
>> Victor,
>>
>> Certainly seems like a common need. I had a similar solution which I
>> used for a while.
>>
>> In the end, however, I found that creating a super-module in the top
>> directory that contains
>> the other git directories as git submodules allowed me to use a
>> standard feature of git to achieve the same effect.
>>
>> So:
>>
>>    git submodule foreach git gc --aggressive
>>
>> I know this won't suit every use case, but it does work in an
>> environment where the set of repos you are operating on have a degree
>> of coherence and it makes sense to set up a submodule for them.  In
>> this particular case this is the only reason why I use submodules - I
>> don't use them for configuration management, for example, simply as a
>> handy way to exploit git submodule foreach.
>>
>> Have you considered using git submodules in this way?
>
> I didn't know you could use them this way, and it's a nicely "Gitonic"
> way of doing it. I don't think this would fit my case, since the repos
> are not much related and it's a more verbose solution which takes
> longer to set up than copying a single script. A compromise could be
> to set up a Git alias `sgit="git submodule foreach git"`, if that'll
> work as expected.
>
> --
> Victor Engmark
>

> I wrote a script for it: fgit
> <https://github.com/l0b0/fgit/blob/master/fgit.sh>. Features include:
> * Runs the Git command given in all specified directories which have a
> .git subdirectory, and warns about any that lack this directory.
> * Should work with any path, containing spaces, newlines or other
> exotic characters.
> * Should work with any Git command that doesn't require the "--"
> separator between the options and arguments.
> * Prints the Git command before running it, for logging and repetition.
> * errexit and nounset are active for each line, with one exception:
> errexit is disabled for the running of the command, to allow it to
> continue to other repositories.

> Victor Engmark <victor.engmark@gmail.com> writes:
>
> [...]
>> I wrote a script for it: fgit
>> <https://github.com/l0b0/fgit/blob/master/fgit.sh>. Features include:
>> * Runs the Git command given in all specified directories which have a
>> .git subdirectory, and warns about any that lack this directory.
>> * Should work with any path, containing spaces, newlines or other
>> exotic characters.
>> * Should work with any Git command that doesn't require the "--"
>> separator between the options and arguments.
>> * Prints the Git command before running it, for logging and repetition.
>> * errexit and nounset are active for each line, with one exception:
>> errexit is disabled for the running of the command, to allow it to
>> continue to other repositories.
>
> Do you think this tool is mature and stable enough to add it to
>
>  https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools
>
> page on Git Wiki?