> On Mar 29, 2015, at 6:53 PM, Brian May <br...@microcomaustralia.com.au> wrote:
> On Mon, 30 Mar 2015 at 06:28 John Whitley <whit...@bangpath.org 
> <mailto:whit...@bangpath.org>> wrote:
> Related thought about vcsh: I've been meaning to add a "vcsh each" command as 
> a generalization of "vcsh {push,pull}".  E.g. "vcsh each git config 
> branch.master.rebase true".  That would be handy in cases like this where I 
> want to run some command in the context of every repository.  Useful for 
> state normalization (e.g. this config change), reporting, etc.  Thoughts?
> This seems like a good thing for me. Less typing then:
> for i in $(vcsh list); do vcsh $i config branch.master.rebase true; done
> Which I think is the simplest way at the moment.

Thanks for the feedback.  I’ll probably have a go at this sometime this week 
and submit a PR.

> Last but not least, you can peruse my root vcsh/mr config at [3].  See the 
> bootstrap.sh script on the bootstrap branch[4] for details.
> Maybe I am getting completely confused here, however what is mr needed for? 
> Think you can do almost everything with just vcsh.

IIRC, that’s true for everything in the default setup up on GitHub, but I 
occasionally use mr-driven repos on specific systems and so keep mr and the 
.mrconfig around in the vcsh-root repo.

— John

vcs-home mailing list

Reply via email to