On Mon, May 2, 2011 at 6:36 PM, Joey Hess wrote:
> micah anderson wrote:
>> > [DEFAULT]
>> > post_checkout = mr addremotes
>> > pre_update = mr addremotes
>
> Of course these run on all repos, like any mr command.
> So, what's really needed is:
>
> [DEFAULT]
> post_checkout = mr -d $MR_REPO addrem
micah anderson wrote:
> > [DEFAULT]
> > post_checkout = mr addremotes
> > pre_update = mr addremotes
Of course these run on all repos, like any mr command.
So, what's really needed is:
[DEFAULT]
post_checkout = mr -d $MR_REPO addremotes
pre_update = mr -d $MR_REPO addremotes
--
see shy jo
sig
On Fri, 29 Apr 2011 19:49:49 -0400, Joey Hess wrote:
> micah anderson wrote:
> > But what if someone adds a new remote? Because I put things in the
> > .mrconfig as a 'post_checkout' the new remote will not be added to the
> > git repository. I could add the remotes twice, in a post_checkout (for
just my 0.1 cents since now it is not recommended way per se since iirc
mr got proper actions (RTFM ;-) ) to be defined to run for such purposes, but
for one of the projects I have done following:
https://github.com/nipy/nipy-suite/blob/master/.mrconfig
[DEFAULT]
lib =
export NIPY=git://github
micah anderson wrote:
> But what if someone adds a new remote? Because I put things in the
> .mrconfig as a 'post_checkout' the new remote will not be added to the
> git repository. I could add the remotes twice, in a post_checkout (for
> the new person who wants to get them all) and then also as a
Hi,
I am working on a project where there are a number of git repositories
that are added at different times, with different remotes being added
(and probably removed) at different times. I thought a nice way to
coordinate this effort was to use 'mr', but I'm stuck on how to do it.
I have a shar
