On Thu, Nov 03, 2011 at 12:22:48PM -0400, Joey Hess wrote:
> Adam Spiers wrote:
> > On Wed, Nov 02, 2011 at 05:02:13PM -0400, Joey Hess wrote:
> > > Adam Spiers wrote:
> > > > I notice that chaining to absolute paths does not work, e.g.:
> > > > Is this a feature or a bug? I would have thought it would be useful
> > > > to chain to absolute paths.
> > >
> > > Probably because nobody noticed since when you're in ~/foo/bar,
> > > ~/foo/bar/.mrconfig will be read anyway without chaining.
> I probably meant to say ~/foo/.mrconfig fwiw.
> > I guess it would really help me if one or two people would be kind
> > enough to briefly describe the way they use mr, e.g.
> > - How is your home directory structured, i.e. where do your mrconfig
> > files and repos live within it, and which mrconfig files point to
> > which repos?
Thanks, this is really useful!
> > - Do you track your mrconfig files with version control?
How do you do that? Are they all in one repo? How do you get each
one into the right subdirectory of ~ ?
> > - Do you frequently use the -d or -c options?
> > - Do you usually cd to a particular directory before running mr, and
> > if so, why?
> I always run mr in the directory I want to affect. Sometimes this
> directory contains many repositories, sometimes only one. The point of
> mr is I don't need to care how many underlying repositories there are.
> If I run it in ~/src/d-i, I want to act on d-i; in
> ~/src/d-i/package/main-menu I'm only dealing with one package; in ~/src
> I want to act on all my source repos.
Very helpful and food for thought, thanks again.
vcs-home mailing list