IMHO, 'darcs init' should warn when it is run in a subfolder of an existing
repository. It currently warns when you are in the folder containing '_darcs',
so it *should* warn if you are in any subfolder of the repository. Either use
the same warning, or something like "Darcs does not support nested repositories.
This is probably not what you want to do.".

For example:
mkdir foo;
cd foo;
darcs init;
mkdir bar;
cd bar;
darcs init;

To fix this, darcs needs to walk up the folder hierarchy checking each parent
folder for an '_darcs' folder.

+1.  While there are legitimate uses for this behaviour, creating a repo
inside another repo is most likely accidental.  Therefore a warning acts
as a useful safety net.

I have create a test script in bugs/ for this issue (see the darcs-users
mailing list).

This should be actually quite easy to implement as we already have code to do
the walking and checking.  We just need to call it and print a warning on Left.

The following patch sent by Alexey Levan <exlevan@gmail.com> updated issue issue1266 with
status=resolved;resolvedin=2.8.0 HEAD

* Resolve issue1266: add a warning about nested repositories 
Ignore-this: f4fdcf0e2d2b46a82da6cee22e945e30