From: Duy Nguyen Date: Wed, 23 Jan 2013 08:39:18 GMT Subject: Re: [PATCH] all: new command used for multi-repo operations Message-ID: In-Reply-To: <1358889019-4554-1-git-send-email-hjemli@gmail.com> On Wed, Jan 23, 2013 at 4:10 AM, Lars Hjemli wrote: > When working with multiple, unrelated (or loosly related) git repos, > there is often a need to locate all repos with uncommitted work and > perform some action on them (say, commit and push). Before this patch, > such tasks would require manually visiting all repositories, running > `git status` within each one and then decide what to do next. > > This mundane task can now be automated by e.g. `git all --dirty status`, > which will find all git repositories below the current directory (even > nested ones), check if they are dirty (as defined by `git diff --quiet && > git diff --cached --quiet`), and for each dirty repo print the path to the > repo and then execute `git status` within the repo. I think it should leave out the execute part. The command, say ls-repo, lists repositories in specified state. The execute part could be easily done by xargs -I{} git --git-dir={} status blah I haven't thought it through. I know xargs does not support chdir'ing into a repo, so maybe a new git-xargs could be introduced for that. But there's still a problem with git-xargs (or git-all), printed paths are relative to the subrepos, not where the git-all/xargs command is executed. This could be confusing. Personally I'd like to do it without chdir. That is xargs -I{} git --git-dir={}/.git --work-tree={} status blah should print paths relative to current working directory even if cwd is outside the repo. -- Duy