Adam Spiers wrote:
> I notice that chaining to absolute paths does not work, e.g.:
>     [$HOME/foo/bar]
>     checkout = ...
>     chain = true
> This is due to the way the chaining code checks for an .mrconfig in
> the chained repository:
>         if ($parameter eq 'chain' &&
>             length $dir && $section ne "DEFAULT" &&
>             -e $dir.$section."/.mrconfig") {
> 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. And there's
rarely a reason to use an absolute path.

Fixed in git.

see shy jo

Attachment: signature.asc
Description: Digital signature

vcs-home mailing list

Reply via email to